-
Notifications
You must be signed in to change notification settings - Fork 407
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
Patternlab init doesn't work on Node 16 #1348
Comments
mfranzke
added a commit
to mfranzke/patternlab-node
that referenced
this issue
Aug 28, 2021
…ab#1348 The installation of the no-emit-webpack-plugin@1 dependency results in a freeze during installation.
antonia-rose
pushed a commit
to quelltexterin/nemo-uikit-workshop
that referenced
this issue
Apr 12, 2023
…ab#1348 (pattern-lab#1349) The installation of the no-emit-webpack-plugin@1 dependency results in a freeze during installation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am using Pattern Lab Node
v5.15.0
onMac
, with Nodev16.8.0
, using aVanilla
Edition.Expected Behavior
Running
npm create pattern-lab
initializes patternlab.Actual Behavior
Running
npm create pattern-lab
initializes patternlab leads to a doesn’t finish (endless spinning blue dots), without any error messages or results on the console.Steps to Reproduce
Run
npm create pattern-lab
and use any of the options (try „Handlebars“ and „Demo patterns“, as the „base patterns“ have another issue on Node 16).Workaround
Until the related pull request gets accepted and merged, you could use the following workaround:
Instead of running
npm create pattern-lab
directly, runnpm i no-emit-webpack-plugin@2 --save-dev
before (and probably annpm init
before, if there's nopackage.json
in your project folder already) and thannpm create pattern-lab && npm uninstall no-emit-webpack-plugin
(as we don't need theno-emit-webpack-plugin
package after the installation has been successfully done).This ensures, that the outdated
no-emit-webpack-plugin
gets used with a newer and non-failing version, mainly for the duration of the installation itself.All credits for this finding go to @awasem.
The text was updated successfully, but these errors were encountered: