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

ELIFECYCLE with Nix NPM when creating TTF #15

Open
jhilker98 opened this issue Jul 19, 2022 · 0 comments
Open

ELIFECYCLE with Nix NPM when creating TTF #15

jhilker98 opened this issue Jul 19, 2022 · 0 comments

Comments

@jhilker98
Copy link

Hey there, thanks for maintaining this.

I've been trying to use my custom build plans whenever I build the font, but when I use version 15.6.0, I get this error after creating the unhinted ttf:

Building process terminated.npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! iosevka@15.6.0 build: `node utility/ensure-verda-exists && verda -f verdafile.js "ttf::josevka-book-sans"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the iosevka@15.6.0 build 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!     /root/.npm/_logs/2022-07-19T16_22_57_793Z-debug.log

Here's the debug log - I found it odd that docker was using Node 14, when the version of node I've installed with nix is v16.15.0.

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/usr/bin/node',
1 verbose cli   '/usr/bin/npm',
1 verbose cli   'run',
1 verbose cli   'build',
1 verbose cli   '--',
1 verbose cli   'ttf::josevka-book-sans'
1 verbose cli ]
2 info using npm@6.14.8
3 info using node@v14.15.1
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle iosevka@15.6.0~prebuild: iosevka@15.6.0
6 info lifecycle iosevka@15.6.0~build: iosevka@15.6.0
7 verbose lifecycle iosevka@15.6.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle iosevka@15.6.0~build: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/tmp/build/Iosevka-15.6.0/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
9 verbose lifecycle iosevka@15.6.0~build: CWD: /tmp/build/Iosevka-15.6.0
10 silly lifecycle iosevka@15.6.0~build: Args: [
10 silly lifecycle   '-c',
10 silly lifecycle   'node utility/ensure-verda-exists && verda -f verdafile.js "ttf::josevka-book-sans"'
10 silly lifecycle ]
11 silly lifecycle iosevka@15.6.0~build: Returned: code: 1  signal: null
12 info lifecycle iosevka@15.6.0~build: Failed to exec build script
13 verbose stack Error: iosevka@15.6.0 build: `node utility/ensure-verda-exists && verda -f verdafile.js "ttf::josevka-book-sans"`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:315:20)
13 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:315:20)
13 verbose stack     at maybeClose (internal/child_process.js:1048:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid iosevka@15.6.0
15 verbose cwd /tmp/build/Iosevka-15.6.0
16 verbose Linux 5.10.16.3-microsoft-standard-WSL2
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "build" "--" "ttf::josevka-book-sans"
18 verbose node v14.15.1
19 verbose npm  v6.14.8
20 error code ELIFECYCLE
21 error errno 1
22 error iosevka@15.6.0 build: `node utility/ensure-verda-exists && verda -f verdafile.js "ttf::josevka-book-sans"`
22 error Exit status 1
23 error Failed at the iosevka@15.6.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

I'm currently using WSL2 with Ubuntu as my distribution - do you have any suggestions for how to fix this? I tried with v15.6.0 and v15.5.2, but I still am not sure. I'm also using Nix with NPM, if that might have anything to do with it.

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

1 participant