-
Notifications
You must be signed in to change notification settings - Fork 12k
support of pnpm when installing a new app #13680
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
A PR to fix the loader resolution will be available shortly. This will enable building to work.
|
…server The dev server requires a node 'events' builtin shim to function. The dev server as written only currently works with package managers that hoist the `events` shim package to an accessible location. Hoisting is unfortantely not standardized and the assumption within the dev server will not hold true for all package managers. Closes angular#13680
…server The dev server requires a node 'events' builtin shim to function. The dev server as written only currently works with package managers that hoist the `events` shim package to an accessible location. Hoisting is unfortunately not standardized and the assumption within the dev server will not hold true for all package managers. Closes angular#13680
…server The dev server requires a node 'events' builtin shim to function. The dev server as written only currently works with package managers that hoist the `events` shim package to an accessible location. Hoisting is unfortunately not standardized and the assumption within the dev server will not hold true for all package managers. Closes angular#13680
…server The dev server requires a node 'events' builtin shim to function. The dev server as written only currently works with package managers that hoist the `events` shim package to an accessible location. Hoisting is unfortunately not standardized and the assumption within the dev server will not hold true for all package managers. Closes angular#13680
…server The dev server requires a node 'events' builtin shim to function. The dev server as written only currently works with package managers that hoist the `events` shim package to an accessible location. Hoisting is unfortunately not standardized and the assumption within the dev server will not hold true for all package managers. Closes angular#13680
I'm having this problem too when trying to use pnpm with angular. Is there any known workaround to solve this error other than shamefully-flatten? Thanks in advance! |
You can just install the missing dependencies (e.g. events), and since it's Webpack that's missing them, you can install to dev dependencies. |
Webpack and its development server assume the presence of two node builtins (`events` & `querystring`). Do to package hoisting npm/yarn will usually place the shims for those two builtins at locations that webpack find them. This is however not guaranteed nor will it work with pnpm which strictly follows the prescribed dependency tree. To remedy this, the specific node shims are enabled only for the specific internal webpack files that are used within the development server. This ensures that the requirements of these files does not pollute the entire application. Fixes angular#13680
Webpack and its development server assume the presence of two node builtins (`events` & `querystring`). Do to package hoisting npm/yarn will usually place the shims for those two builtins at locations that webpack find them. This is however not guaranteed nor will it work with pnpm which strictly follows the prescribed dependency tree. To remedy this, the specific node shims are enabled only for the specific internal webpack files that are used within the development server. This ensures that the requirements of these files does not pollute the entire application. Fixes angular#13680
Webpack and its development server assume the presence of two node builtins (`events` & `querystring`). Do to package hoisting npm/yarn will usually place the shims for those two builtins at locations that webpack find them. This is however not guaranteed nor will it work with pnpm which strictly follows the prescribed dependency tree. To remedy this, the specific node shims are enabled only for the specific internal webpack files that are used within the development server. This ensures that the requirements of these files does not pollute the entire application. Fixes angular#13680
Webpack and its development server assume the presence of two node builtins (`events` & `querystring`). Do to package hoisting npm/yarn will usually place the shims for those two builtins at locations that webpack find them. This is however not guaranteed nor will it work with pnpm which strictly follows the prescribed dependency tree. To remedy this, the specific node shims are enabled only for the specific internal webpack files that are used within the development server. This ensures that the requirements of these files does not pollute the entire application. Fixes #13680
Webpack and its development server assume the presence of two node builtins (`events` & `querystring`). Do to package hoisting npm/yarn will usually place the shims for those two builtins at locations that webpack find them. This is however not guaranteed nor will it work with pnpm which strictly follows the prescribed dependency tree. To remedy this, the specific node shims are enabled only for the specific internal webpack files that are used within the development server. This ensures that the requirements of these files does not pollute the entire application. Fixes #13680
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. |
🚀 Feature request
Command
Description
a new app or library generated with CLI 7.3.1 but installed with pnpm doesn't compile.
result:
From what i read, it would have to do with how angular is declaring its dependencies in the generated package.json.
Describe alternatives you've considered
There is a workaround within pnpm. One can use the shamefully-flatten install flag so that node_modules are laid out like yarn or npm. But it is a shame to have to do that right ? :).
But this workaround only works for angular application (serve and build), not libraries
The text was updated successfully, but these errors were encountered: