You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the awesome product!! I've been working my way through the excellent demo material to put together a presentation for a small JavaScript meetup I organize. I completed the steps up to the Build Routes stage, at which point I realized I needed to have my component published on NPM to proceed. Everything was pretty straightforward but when I ran $ npm publish the process failed. The cause seems to be within gulp prepublish. I wasn't able to find any info on submitting issues, so I figured this was as good a place as any. I'm on Windows 10 but also have access to a Linux setup so I'll try to replicate the steps there and see if it succeeds. In the meantime, please feel free to contact me for additional info.
Here are the contents of the npm debug log:
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'publish' ]
2 info using [email protected]
3 info using [email protected]
4 verbose publish [ '.' ]
5 silly cache add args [ '.', null ]
6 verbose cache add spec .
7 silly cache add parsed spec Result {
7 silly cache add raw: '.',
7 silly cache add scope: null,
7 silly cache add escapedName: null,
7 silly cache add name: null,
7 silly cache add rawSpec: '.',
7 silly cache add spec: 'C:\\Users\\blake\\Documents\\electrode_projects\\seajs_homepage_demo_component\\seajsws-component',
7 silly cache add type: 'directory' }
8 verbose addLocalDirectory C:\Users\blake\AppData\Roaming\npm-cache\seajsws-component\1.0.0\package.tgz not in flight; packing
9 verbose correctMkdir C:\Users\blake\AppData\Roaming\npm-cache correctMkdir not in flight; initializing
10 info lifecycle [email protected]~prepublish: [email protected]
11 verbose lifecycle [email protected]~prepublish: unsafe-perm in lifecycle true
12 verbose lifecycle [email protected]~prepublish: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\Users\blake\Documents\electrode_projects\seajs_homepage_demo_component\seajsws-component\node_modules\.bin;C:\Users\blake\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\local\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Users\blake\bin;C:\Program Files\cmder\vendor\conemu-maximus5\ConEmu\Scripts;C:\Program Files\cmder\vendor\conemu-maximus5;C:\Program Files\cmder\vendor\conemu-maximus5\ConEmu;C:\Program Files\Git\usr\bin;C:\Program Files (x86)\Intel\iCLS Client;C:\Program Files\Intel\iCLS Client;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\nodejs;C:\Program Files (x86)\Heroku\bin;C:\Program Files\Git\cmd;C:\Users\blake\AppData\Local\atom\bin;C:\Users\blake\AppData\Roaming\npm;%USERPROFILE%\AppData\Local\Microsoft\WindowsApps;C:\Program Files\Git\usr\bin\vendor_perl;C:\Program Files\Git\usr\bin\core_perl
13 verbose lifecycle [email protected]~prepublish: CWD: C:\Users\blake\Documents\electrode_projects\seajs_homepage_demo_component\seajsws-component
14 silly lifecycle [email protected]~prepublish: Args: [ '/d /s /c', 'gulp prepublish' ]
15 silly lifecycle [email protected]~prepublish: Returned: code: 1 signal: null
16 info lifecycle [email protected]~prepublish: Failed to exec prepublish script
17 error addLocal Could not install C:\Users\blake\Documents\electrode_projects\seajs_homepage_demo_component\seajsws-component
18 verbose stack Error: [email protected] prepublish: `gulp prepublish`
18 verbose stack Exit status 1
18 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:255:16)
18 verbose stack at emitTwo (events.js:106:13)
18 verbose stack at EventEmitter.emit (events.js:191:7)
18 verbose stack at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:40:14)
18 verbose stack at emitTwo (events.js:106:13)
18 verbose stack at ChildProcess.emit (events.js:191:7)
18 verbose stack at maybeClose (internal/child_process.js:877:16)
18 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
19 verbose pkgid [email protected]
20 verbose cwd C:\Users\blake\Documents\electrode_projects\seajs_homepage_demo_component\seajsws-component
21 error Windows_NT 10.0.14393
22 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "publish"
23 error node v6.9.1
24 error npm v3.10.8
25 error code ELIFECYCLE
26 error [email protected] prepublish: `gulp prepublish`
26 error Exit status 1
27 error Failed at the [email protected] prepublish script 'gulp prepublish'.
27 error Make sure you have the latest version of node.js and npm installed.
27 error If you do, this is most likely a problem with the seajsws-component package,
27 error not with npm itself.
27 error Tell the author that this fails on your system:
27 error gulp prepublish
27 error You can get information on how to open an issue for this project with:
27 error npm bugs seajsws-component
27 error Or if that isn't available, you can get their info via:
27 error npm owner ls seajsws-component
27 error There is likely additional logging output above.
28 verbose exit [ 1, true ]
And here is the start of the error message that was printed to the console:
$ npm publish
> [email protected] prepublish C:\Users\blake\Documents\electrode_projects\seajs_homepage_demo_component\seajsws-component
> gulp prepublish
[18:47:02] Using gulpfile ~\Documents\electrode_projects\seajs_homepage_demo_component\seajsws-component\gulpfile.js
[18:47:02] Starting 'prepublish'...
[18:47:02] Starting 'npm:prepublish'...
[18:47:02] Starting 'build-lib-$deps$'...
[18:47:02] Starting '~production-env'...
[18:47:02] Finished '~production-env' after 143 μs
[18:47:02] Finished 'build-lib-$deps$' after 3.05 ms
[18:47:02] Starting 'build-lib'...
[18:47:02] Starting 'clean-lib'...
[18:47:02] Finished 'clean-lib' after 31 ms
[18:47:02] Starting 'babel-src-step'...
Error: EPERM: operation not permitted, mkdir 'C:\Users\blake\Documents\electrode_projects\seajs_homepage_demo_component\seajsws-component\lib\components'
at Error (native)
at Object.fs.mkdirSync (fs.js:922:18)
at sync (C:\Users\blake\Documents\electrode_projects\seajs_homepage_demo_component\seajsws-component\node_modules\mkdirp\index.js:71:13)
at outputFileSync (C:\Users\blake\Documents\electrode_projects\seajs_homepage_demo_component\seajsws-component\node_modules\output-file-sync\index.js:44:24)
at write (C:\Users\blake\Documents\electrode_projects\seajs_homepage_demo_component\seajsws-component\node_modules\babel-cli\lib\babel\dir.js:34:5)
at handleFile (C:\Users\blake\Documents\electrode_projects\seajs_homepage_demo_component\seajsws-component\node_modules\babel-cli\lib\babel\dir.js:44:7)
at C:\Users\blake\Documents\electrode_projects\seajs_homepage_demo_component\seajsws-component\node_modules\babel-cli\lib\babel\dir.js:63:11
at arrayEach (C:\Users\blake\Documents\electrode_projects\seajs_homepage_demo_component\seajsws-component\node_modules\lodash\lodash.js:537:11)
at Function.forEach (C:\Users\blake\Documents\electrode_projects\seajs_homepage_demo_component\seajsws-component\node_modules\lodash\lodash.js:9344:14)
at C:\Users\blake\Documents\electrode_projects\seajs_homepage_demo_component\seajsws-component\node_modules\babel-cli\lib\babel\dir.js:61:11
[18:47:04] 'babel-src-step' errored after 2.41 s
[18:47:04] Error: command exit code 1```
Thanks!
The text was updated successfully, but these errors were encountered:
Hello,
Thanks for the awesome product!! I've been working my way through the excellent demo material to put together a presentation for a small JavaScript meetup I organize. I completed the steps up to the Build Routes stage, at which point I realized I needed to have my component published on NPM to proceed. Everything was pretty straightforward but when I ran
$ npm publish
the process failed. The cause seems to be withingulp prepublish
. I wasn't able to find any info on submitting issues, so I figured this was as good a place as any. I'm on Windows 10 but also have access to a Linux setup so I'll try to replicate the steps there and see if it succeeds. In the meantime, please feel free to contact me for additional info.Here are the contents of the npm debug log:
And here is the start of the error message that was printed to the console:
The text was updated successfully, but these errors were encountered: