!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

212 Members
62 Servers

Load older messages


SenderMessageTime
12 May 2023
@lily:lily.flowersLily Foster
In reply to @hexa:lossy.network
Lily Foster: wondering if you're well enough to finish up https://github.com/NixOS/nixpkgs/pull/230188 🙂
Done! It looked good now
17:10:42
@ambroisie:belanyi.fr@ambroisie:belanyi.fr
In reply to @ambroisie:belanyi.fr
That's what I remembered, I'll open one when I get back to my computer 👌
Done #231513
18:00:43
@federicodschonborn:matrix.orgFederico Damián Schonborn changed their profile picture.19:34:18
@federicodschonborn:matrix.orgFederico Damián Schonborn changed their display name from Federico Schonborn to Federico Damián Schonborn.19:35:01
14 May 2023
@jfvillablanca:matrix.orgjfvillablanca joined the room.11:38:40
16 May 2023
@hexa:lossy.networkhexa

getting the following error during node run build

sh: line 1: /build/source/node_modules/.bin/webpack: cannot execute: required file not found

16:00:28
@hexa:lossy.networkhexahttps://github.com/NixOS/nixpkgs/pull/232255#issuecomment-154992849316:01:27
@lily:lily.flowersLily Foster
In reply to @hexa:lossy.network

getting the following error during node run build

sh: line 1: /build/source/node_modules/.bin/webpack: cannot execute: required file not found

I believe https://github.com/NixOS/nixpkgs/pull/206477 probably fixes that if you want to give it a review :)
16:01:33
@lily:lily.flowersLily Foster(I apologize in advance for you having to rebuild nodejs...)16:03:33
@hexa:lossy.networkhexa
In reply to @lily:lily.flowers
I believe https://github.com/NixOS/nixpkgs/pull/206477 probably fixes that if you want to give it a review :)
same as before 😄
18:17:13
@lily:lily.flowersLily FosterDamn. I'll look later today or tomorrow then18:30:20
@hexa:lossy.networkhexaanyway18:30:58
@hexa:lossy.networkhexathe file is a symlink to her18:31:02
@hexa:lossy.networkhexa * the file is a symlink to here18:31:02
@hexa:lossy.networkhexa

-rwxr-xr-x 1 nixbld nixbld 3.9K May 16 15:57 node_modules/webpack/bin/webpack.js

18:31:06
@hexa:lossy.networkhexathat file is 18:31:14
@hexa:lossy.networkhexa

node_modules/webpack/bin/webpack.js: a /nix/store/6aphgr19pzc8v416zaf6vbs7r9jsbajp-nodejs-18.16.0/bin/node script, ASCII text executable

18:31:16
@hexa:lossy.networkhexaand starts like so18:31:29
@hexa:lossy.networkhexa
#!/nix/store/6aphgr19pzc8v416zaf6vbs7r9jsbajp-nodejs-18.16.0/bin/node

/**
 * @param {string} command process to run
 * @param {string[]} args command line arguments
 * @returns {Promise<void>} promise
 */
const runCommand = (command, args) => {
        const cp = require("child_process");
        return new Promise((resolve, reject) => {
18:31:33
@hexa:lossy.networkhexaand I can start that interpreter18:31:53
@hexa:lossy.networkhexa
❯ /nix/store/6aphgr19pzc8v416zaf6vbs7r9jsbajp-nodejs-18.16.0/bin/node
Welcome to Node.js v18.16.0.
Type ".help" for more information.
18:32:00
@hexa:lossy.networkhexahttps://github.com/django-hijack/django-hijack/blob/master/package.json#L518:36:05
@hexa:lossy.networkhexathe build command18:36:11
17 May 2023
@hexa:lossy.networkhexaso sorry, but I'm running into another problem I don't understand19:00:14
@hexa:lossy.networkhexa
bokehjs> unpacking sources
bokehjs> unpacking source archive /nix/store/bibdvavvcjjm5rgs1xy2x4ckxg3jkchj-source
bokehjs> source root is source/bokehjs
bokehjs> patching sources
bokehjs> Executing npmConfigHook
bokehjs> Configuring npm
bokehjs> Validating consistency between /build/source/bokehjs/package-lock.json and /nix/store/14kzn4a79fgaknfj3nd84a3j4szxf371-bokehjs-3.1.1-npm-deps/package-lock.json
bokehjs> Making cache writable
bokehjs> Installing dependencies
bokehjs> npm WARN deprecated source-map-resolve@0.6.0: See https://github.com/lydell/source-map-resolve#deprecated
bokehjs> npm ERR! code ENOTCACHED
bokehjs> npm ERR! request to https://registry.npmjs.org/p-map failed: cache mode is 'only-if-cached' but no cached response is available.
bokehjs> 
bokehjs> npm ERR! A complete log of this run can be found in:
bokehjs> npm ERR!     /build/cache/_logs/2023-05-17T18_59_40_525Z-debug-0.log
bokehjs> 
bokehjs> ERROR: npm failed to install dependencies
bokehjs> 
bokehjs> Here are a few things you can try, depending on the error:
bokehjs> 1. Set `makeCacheWritable = true`
bokehjs>   Note that this won't help if npm is complaining about not being able to write to the logs directory -- look above that for the actual error.
bokehjs> 2. Set `npmFlags = [ "--legacy-peer-deps" ]`
bokehjs> 
19:00:18
@hexa:lossy.networkhexa
    npmFlags = [ "--legacy-peer-deps" ];

    makeCacheWritable = true;
19:00:47
@hexa:lossy.networkhexahttps://github.com/bokeh/bokeh/blob/3.1.1/bokehjs/package.json19:01:25
@lily:lily.flowersLily Foster
In reply to @hexa:lossy.network
https://github.com/bokeh/bokeh/blob/3.1.1/bokehjs/package.json
npm workspaces. I haven't done a deep dive yet to figure out why npm gets too spooked to use the cache when workspaces are involved like this. The method to specify a workspace package like from https://github.com/NixOS/nixpkgs/pull/218923 may help
19:18:32
@lily:lily.flowersLily Foster dotlambda: If it helps for fixing the above package, would it be okay if I separate out the change to add an npmWorkspace argument from that bitwarden-cli PR and make my own separate PR? (or alternatively if you have time to respond to the review comments, we can keep the work in that PR) 19:21:05
@lily:lily.flowersLily Foster
In reply to @hexa:lossy.network
so sorry, but I'm running into another problem I don't understand
No sorry needed, btw. Always appreciate people bringing forward issues/edge cases to help with the tooling
19:21:52

Show newer messages


Back to Room ListRoom Version: 6