Do you want to request a feature or report a bug?
What is the current behavior?
A package being installed from the NPM registry with bundled dependencies will look for the bundled dependencies on NPM registry instead of using the bundled versions. If modules don’t exist on the npm registry, the install fails saying
error Couldn't find package "bundled-package@*" required by "firstname.lastname@example.org" on the "npm" registry.
If the current behavior is a bug, please provide the steps to reproduce.
yarn add win-bt
This is my module that I’ve published to npm, it uses bundled dependencies for some windows specific features, so unfortunately this will only work on windows. There are some other prerequisites that are necessary for a full successful install, but it doesn’t get to any of those before this bundled dependencies error so it shouldn’t be an issue. Alternately, you could potentially use some other module that has bundled dependencies on npm, I just don’t know of any specifically that do. Regardless, all you have to do is
yarn add like so and the error shows up.
What is the expected behavior?
Expected to fetch the module and use the dependencies bundled therein instead of looking on NPM for them.
Please mention your node.js, yarn and operating system version.
node:8.9.1 yarn:1.5.1 and 1.7.0 os: Windows 10 v1803 (build 17134.48)