-
Notifications
You must be signed in to change notification settings - Fork 12
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
npm install errors #2
Comments
I got it to work, but I'm using a forked version of your repo with some additional modifications. Here's what I had to do:
{
var nib = require('nib');
to .pipe(stylus({ use: nib() })) |
Well the repo is quite unmaintained, and - like you noticed - some libraries changed since. Maybe you'd like to fork and create a pull request with your fixes? |
I just cloned your repository, ran npm install (using npm version 2.10.1) , and get this output:
npm install
npm WARN package.json [email protected] No license field.
npm WARN deprecated [email protected]: Please use gulp-cssnano instead.
npm WARN deprecated [email protected]: package is no longer maintained
npm WARN deprecated [email protected]: lodash@<2.0.0 is no longer maintained. Upgrade to lodash@^3.0.0
npm WARN deprecated [email protected]: Use the "buffer" module (https://www.npmjs.com/package/buffer) instead
npm ERR! Linux 4.1.5-x86_64-linode61
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v0.12.4
npm ERR! npm v2.10.1
npm ERR! code E404
npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/esprima-six
npm ERR! 404
npm ERR! 404 'esprima-six' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'syntax-error'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! Please include the following file with any support request:
npm ERR! /var/www/dockvine/backbone-marionette-gulp-seed/npm-debug.log
The text was updated successfully, but these errors were encountered: