-
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
uikit-workshop 5.5.0 crashes during serve
when adding an empty pattern file
#1114
Comments
Thanks for submitting this @ringods! We'll need to do some digging however my initial suspicion is that this might have something to do with Node v13 (vs Node v12). 🤔 |
@sghoweri In the meantime, I switched to Node v12 too and the problems are gone. So you suspicion makes sense. ;-) |
Hi there. I am on node v12.3.6 and the error pops up again. Any suggestions? |
Happening for me too. Just randomly happens without any rhyme or reason...even after just a simple edit to an HBS file. Very annoying since it constantly interrupts my workflow. :(
Running on Node 14.12.0 with the following Pattern Lab dependencies:
Being that it happens on other versions of Node makes it rather unlikely it's just a simple Node issue. :P |
I am getting this error on Node v 12.16.3 with the latest Pattern Lab, as well. The issue persists even when rolling back to 5.13.1 as suggested above. This is on a fresh install. |
@jeffwhitfield @sdlambert, can one of you tell me what exactly you did and which operating system you use? I tested this with a fresh installation and added, deleted, and even renamed empty patterns or any other pattern. |
@joekarasek I'm currently on macOS Big Sur v11.1 using Node v12.2. Here's what's in my
|
Yeah, it's virtually unusable now due to all the Might be due to issues with Webpack. As it stands though, I'll likely need to just stop using Pattern Lab till it's fixed. :( |
Happens from time to time in my setup as well: {
"name": "liquid-core",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1",
"pl:build": "patternlab build --config ./patternlab-config.json",
"pl:publish": "patternlab build --config ./patternlab-public.json",
"pl:help": "patternlab --help",
"pl:install": "patternlab install --config ./patternlab-config.json",
"pl:serve": "patternlab serve --config ./patternlab-config.json",
"gulp:serve": "gulp",
"gulp:serveStyles2": "gulp serveStyles2",
"pl:version": "patternlab --version"
},
"keywords": [],
"author": "",
"license": "ISC",
"dependencies": {
"@pattern-lab/cli": "^5.14.1",
"@pattern-lab/core": "^5.14.1",
"@pattern-lab/engine-handlebars": "^5.14.0",
"@pattern-lab/uikit-workshop": "^5.14.1",
"postcss": "^8.2.6"
},
"devDependencies": {
"gulp": "^4.0.2",
"gulp-autoprefixer": "^7.0.1",
"gulp-load-plugins": "^2.0.6",
"gulp-plumber": "^1.2.1",
"gulp-postcss": "^9.0.0",
"gulp-sass": "^4.1.0",
"gulp-sourcemaps": "^3.0.0",
"node-sass": "^5.0.0",
"npm-run-all": "^4.1.5"
}
} Tested NodeJS versions: 12, 14
|
I'm sadly only able to reproduce this issue sporadically, but will provide updates to packages of the main possible causes (chokidar and webpack) with some merge requests. |
@mfranzke What I recognized is that it happens when having an issue in the handlebars file in my case and save it. At least what I have recognized it. |
@StfBauer are you still experiencing this even after the latest updates, or could we close this ticket ? |
@jeffwhitfield are you still experiencing this even after the latest updates, or could we close this ticket ? |
@mfranzke Never had this issue with the current version. |
I am using Pattern Lab Node
v5.5.0
onMac
, with Nodev13.5.0
, using aCustom
Edition.Expected Behavior
patternlab serve
should rebuild and reload correctly when I add a new empty pattern in any of the pattern folders.Actual Behavior
When I add an empty pattern file in any of the pattern folders, the patterns are rebuilt but then
patternlab serve
crashes on me:Steps to Reproduce
Use
@patternlab/uikit-workshop
v5.5.0 indevDependencies
of my setup. When I revert to v5.4.0, the error is gone.The text was updated successfully, but these errors were encountered: