Skip to content
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 fauxton fails directly #1149

Closed
Wildfirefox opened this issue Oct 29, 2018 · 12 comments
Closed

npm install fauxton fails directly #1149

Wildfirefox opened this issue Oct 29, 2018 · 12 comments

Comments

@Wildfirefox
Copy link

Wildfirefox commented Oct 29, 2018

Hello everybody,

Expected Behavior:
The command npm install fauxton --save installs the fauxton package into a project.

Current behavior:
The command npm install fauxton --save does not install the package because of a failing install of the dev dependency @webcomponents/url

Steps to reproduce:
npm init a empty project then run the command: npm install --save fauxton

This is the output of the command line:

C:\Users\w010563\Desktop\test>npm install --save fauxton
npm WARN deprecated babel@6.23.0: In 6.x, the babel package has been deprecated in favor of babel-cli. Check https://opencollective.com/babel to support the Babel maintainers
npm WARN deprecated babel-preset-es2015@6.24.1: 🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!
npm WARN deprecated react-range@0.0.7: This module is now under the @mapbox namespace: install @mapbox/react-range instead

@webcomponents/url@0.7.1 prepack C:\Users\w010563\AppData\Roaming\npm-cache_cacache\tmp\git-clone-882bcb4c
npm run build

@webcomponents/url@0.7.1 build C:\Users\w010563\AppData\Roaming\npm-cache_cacache\tmp\git-clone-882bcb4c
gulp

Der Befehl "gulp" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @webcomponents/url@0.7.1 build: gulp
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @webcomponents/url@0.7.1 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\w010563\AppData\Roaming\npm-cache_logs\2018-10-29T08_22_31_084Z-debug.log
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! code ENOPACKAGEJSON
npm ERR! package.json Non-registry package missing package.json: @webcomponents/url@git+https://github.com/webcomponents/URL.git.
npm ERR! package.json npm can't find a package.json file in your current directory.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\w010563\AppData\Roaming\npm-cache_logs\2018-10-29T08_22_31_178Z-debug.log

@popojargo
Copy link
Member

popojargo commented Oct 29, 2018

We changed our dependency for webcomponent/uri to use the npm link instead of the git url back in june. We would need to publish the latest release: c3d590f

@wohali
Copy link
Member

wohali commented Oct 29, 2018

@popojargo Bump Fauxton anytime you need to - you just need to issue a PR against apache/couchdb to bump the version tag in this line

@popojargo
Copy link
Member

@wohali Actually, I don't think it's necessary to bump the version. We just need to publish the latest release to npm. Any idea how to do that?

@wohali
Copy link
Member

wohali commented Oct 29, 2018

@popojargo I don't have access, but I expect @garrensmith does.

@wohali
Copy link
Member

wohali commented Oct 29, 2018

Also @michellephung might have access?

@michellephung
Copy link
Member

michellephung commented Oct 29, 2018

@popojargo try this to publish

$ npm version
$ git log
$ git tag
$ git show
$ git push --tags upstream master <—pushes tags to git origin (upstream should be apache/couch-fauxton)
$ npm publish

@popojargo
Copy link
Member

@michellephung I don't have the permissions to publish. Do I need to be a contributor?

@michellephung
Copy link
Member

@popojargo hmm.. i think so. let me try an add you

@michellephung
Copy link
Member

michellephung commented Oct 29, 2018

ok so i don't know how to do that but i did release a new tag with your latest tag

@popojargo
Copy link
Member

@Wildfirefox let us know if the updated package works on your side.

@wohali
Copy link
Member

wohali commented Oct 30, 2018

@popojargo Check your apache.org email address, we need your help to get you npm access.

@Wildfirefox
Copy link
Author

@popojargo It seems to work with the updated package. Thx for the fast reply on this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants