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

Repo installs fail #33

Open
jayvdb opened this issue Dec 12, 2018 · 2 comments
Open

Repo installs fail #33

jayvdb opened this issue Dec 12, 2018 · 2 comments

Comments

@jayvdb
Copy link
Contributor

jayvdb commented Dec 12, 2018

It can be quite helpful to do repo installs

$ npm -g i '8eecf0d2/netlify-local'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/netlify-local/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! path /usr/local/lib/node_modules/netlify-local/.dist/cli.js
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod '/usr/local/lib/node_modules/netlify-local/.dist/cli.js'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2018-12-12T13_20_46_337Z-debug.log

Tail of the debug log

10944 info linkStuff [email protected]
10945 silly linkStuff [email protected] has /usr/local/lib/node_modules/netlify-local/node_modules as its parent node_modules
10946 silly linkStuff [email protected] is part of a global install
10947 silly linkStuff [email protected] is installed into a global node_modules
10948 verbose linkBins [ { webpack: './bin/webpack.js' },
10948 verbose linkBins   '/usr/local/lib/node_modules/netlify-local/node_modules/.bin',
10948 verbose linkBins   false ]
10949 silly build [email protected]
10950 info linkStuff [email protected]
10951 silly linkStuff [email protected] has /usr/local/lib/node_modules as its parent node_modules
10952 silly linkStuff [email protected] is part of a global install
10953 silly linkStuff [email protected] is installed into a global node_modules
10954 silly linkStuff [email protected] is installed into the top-level global node_modules
10955 verbose linkBins [ { 'netlify-local': '.dist/cli.js' }, '/usr/local/bin', true ]
10956 timing action:build Completed in 126ms
10957 verbose unlock done using /root/.npm/_locks/staging-3a08f0df5026584d.lock for /usr/local/lib/node_modules/.staging
10958 timing stage:rollbackFailedOptional Completed in 652ms
10959 timing stage:runTopLevelLifecycles Completed in 46801ms
10960 warn optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/netlify-local/node_modules/fsevents):
10961 warn notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
10962 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid OS:    darwin
10962 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid Arch:  any
10962 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual OS:   linux
10962 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual Arch: x64
10963 verbose stack Error: ENOENT: no such file or directory, chmod '/usr/local/lib/node_modules/netlify-local/.dist/cli.js'
10964 verbose cwd /root
10965 verbose Linux 4.19.7-1-default
10966 verbose argv "/usr/bin/node10" "/usr/bin/npm-default" "-g" "i" "8eecf0d2/netlify-local"
10967 verbose node v10.13.0
10968 verbose npm  v6.4.1
10969 error path /usr/local/lib/node_modules/netlify-local/.dist/cli.js
10970 error code ENOENT
10971 error errno -2
10972 error syscall chmod
10973 error enoent ENOENT: no such file or directory, chmod '/usr/local/lib/node_modules/netlify-local/.dist/cli.js'
10974 error enoent This is related to npm not being able to find a file.
10975 verbose exit [ -2, true ]
@8eecf0d2
Copy link
Owner

My main reason for not committing build output is I don't see git not as a distribution target for this project (although I have used git for distribution in the past.)

If you have a real use case I'd be open to changing my mind but otherwise prefer to keep ignoring build output.

@jayvdb
Copy link
Contributor Author

jayvdb commented Dec 15, 2018

It is usually possible to support repo installs without pushing build artifacts, using post-install steps. I've only done it a few times, so I cant be certain it will work here. I'm happy to give it a go.

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

2 participants