-
Notifications
You must be signed in to change notification settings - Fork 21
Installation as dependency doesn't work #17
Comments
Just to clarify - this isn't supposed to be working right now. For the time being, the only way to use Pattern Lab Node Editions is as standalone projects. You can still download the package or clone the repo and run |
I guess this could be closed by adding some informative text that I would have read and been very thankfull for the time I would have saved ;-) But please keep up the good work and thank you. |
I'm surprised every time I'm remembered about this strange distribution strategy. I really don't get it, why nobody thought of the scenario, that somebody would like to add patternlab as a devDependency to a frontend package and generate the patternlab from the CSS from the package and the patterns without copying all the stuff from the NPM package and forcing the users to make manual updates instead of allowing updates through NPM. The patternlab CLI doesn't help in this case. I just want to put my patterns somewhere and give grunt the path to the pattern directory and the CSS. It could be so simple. |
@DaSchTour comments like this do nothing but dishearten maintainers. We are actively working (almost exclusively by donating our free time) on making PL perform better under these exact use cases and care very much about getting it right. |
@DaSchTour I'd also like to point you to https://github.com/pattern-lab/patternlab-node-cli/wiki/Use-Cases which is currently under construction as a place to document all use cases we want to cover with PL Node 3.0 I welcome your input there |
I am using Edition Node Grunt
v1.1.0
onWindows
, with Nodev6.5.0
.Expected Behavior
Installation as dependecy works
Actual Behavior
postinstall script throws Exception after installation
Steps to Reproduce
npm-debug.txt
The text was updated successfully, but these errors were encountered: