npm link issues?

[jrm2k6]

I am still struggling with some npm link issues when trying to test a package locally, in an example app using webpack. Do you have any advice? I tried many things unsucessfully.

[rstacruz]

I'm not the best Webpack expert, but I assume you only need to do:

$ cd ~/sub_project
$ npm link  # makes sub_project available later

$ cd ~/super_project
$ # add `sub_project` to your package.json dependencies
$ npm link sub_project  # makes a link to ~/sub_project

...and continue using sub_project as needed.

[xavhan]

try with

//up in the requires const path = require('path');
resolve: { fallback: path.join(__dirname, "node_modules") },
resolveLoader: { fallback: path.join(__dirname, "node_modules") },

in your config object.

cf: https://webpack.github.io/docs/troubleshooting.html

[jrm2k6]

I tried that already and it didn't seem to work sadly.

…

On Fri, Dec 23, 2016 at 1:19 AM Xavier Haniquaut ***@***.***> wrote: try with //up in the requires const path = require('path'); resolve: { fallback: path.join(__dirname, "node_modules") }, resolveLoader: { fallback: path.join(__dirname, "node_modules") }, in your config object. cf: https://webpack.github.io/docs/troubleshooting.html — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABCaY-vQ5kcxTCcredqG-bE2AMtE2HOqks5rK5IXgaJpZM4LTT-g> .

[rstacruz]

Wish I can help, but this issue's beyond my webpack experience level.

[rstacruz]

If the solutions me and @xavhan suggested didn't work for you, it might be a Webpack bug or a fault in your config/setup. I suggest trying to set up an isolated case and reporting your findings to the Webpack maintainers. Good luck!