-
Notifications
You must be signed in to change notification settings - Fork 12k
Error: Cannot find module 'portfinder' with Webpack release and NPM 2 #1770
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I had the same issue and needed to update npm. |
@cmjacques It upgrades NPM to 3. The issue applies to NPM 2.x which may be used on purpose. |
NPM3 is needed, yes. #1748 adds that requirement to the README. |
@filipesilva But it works flawlessly with NPM 2 in other respects. Relying on Forcing NPM 3 for globally installed packages is the last thing the one may want, because it turns global |
I'm sorry but there is just no way around NPM3. It's a hard dependency, and it has nothing to do with |
+1 |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Windows 7
ng --version
. If there's nothing outputted, please runin a Terminal:
node --version
and paste the result here:angular-cli: 1.0.0-beta.11-webpack.2
node: 6.2.2
npm: 2.15.6
do on your code? etc.
npm i -g [email protected]
ng
more information.
The problem occurs with Webpack release and NPM 2.
ember-cli
depends onportfinder
package and has it innode_modules
after installation, butangular-cli
expectsportfinder
to be located in itsnode_modules
.The problem can be solved by installing
portfinder
package manually inangular-cli
or parentnode_modules
directory.The text was updated successfully, but these errors were encountered: