Skip to content

Local testing breaks a different way (css build fails) #28

@exitmouse

Description

@exitmouse

If I manually increment parallelshell to 3.0.0 like Geoffrey said, then I get:

> static-fp@1.0.0 css:min /home/jselover/Projects/static-fp
> cleancss static/css/style.css > static/css/style.min.css

sh: cleancss: コマンドが見つかりません [editor's note: "command not found"]
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! static-fp@1.0.0 css:min: `cleancss static/css/style.css > static/css/style.min.css`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the static-fp@1.0.0 css:min script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/jselover/.npm/_logs/2017-09-03T17_33_19_386Z-debug.log

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions