-
Notifications
You must be signed in to change notification settings - Fork 33
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
Error when attempting to build styleguide #22
Comments
Hi morishi, As you might have already known, this problem seems related to a flat node_modules in npm v3. This means it should not to depend a simple path as a string like here because now it couldn't be sure where is the child module in whether same directory or parent directory or the other case or not. Thanks! |
@watilde Thank you for your advice! I will learn npm v3 in your awesome slides :) |
@faceleg Please update postcss-style-guide to v0.9.1. |
Will do, thanks! |
Hilariously, this failed for me just when I was demoing it to a fellow programmer. |
Finally, can I please have a link to the slides? |
@morishitter Oh you also need to take in this patch to use the |
Is there something I'm missing?
[19:47:18] Error: ENOENT: no such file or directory, open '/Users/faceleg/Sync/faceleg/Work//services/web-frontend/node_modules/postcss-style-guide/node_modules/psg-theme-default/template.ejs'
at Error (native)
at Object.fs.openSync (fs.js:584:18)
at Object.fs.readFileSync (fs.js:431:33)
at /Users/faceleg/Sync/faceleg/Work//services/web-frontend/node_modules/postcss-style-guide/index.js:34:27
at creator (/Users/faceleg/Sync/faceleg/Work//services/web-frontend/node_modules/postcss/lib/postcss.js:60:39)
at Function.postcss.plugin (/Users/faceleg/Sync/faceleg/Work//services/web-frontend/node_modules/postcss/lib/postcss.js:66:23)
at Object. (/Users/faceleg/Sync/faceleg/Work//services/web-frontend/node_modules/postcss-style-guide/index.js:12:26)
at Module._compile (module.js:425:26)
at Object.Module._extensions..js (module.js:432:10)
at Module.load (module.js:356:32)
The text was updated successfully, but these errors were encountered: