!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

194 Members
56 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
8 Mar 2024
@hexa:lossy.networkhexa
In reply to @lily:lily.flowers
yeah i'm just messing with you :)
same, same
22:56:21
@hexa:lossy.networkhexa
pretix> running build
pretix> npm WARN reify Removing non-directory /build/source/src/pretix/static.dist/node_prefix/node_modules
pretix> npm ERR! code EAI_AGAINn: sill reify mark deleted [ [[Kectory /build/sour
pretix> npm ERR! syscall getaddrinfo
pretix> npm ERR! errno EAI_AGAIN
pretix> npm ERR! request to https://registry.npmjs.org/yallist/-/yallist-2.1.2.tgz failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org
pretix> 
pretix> npm ERR! Log files were not written due to an error writing to the directory: /homeless-shelter/.npm/_logs
pretix> npm ERR! You can rerun the command with `--loglevel=verbose` to see the logs in your terminal
23:20:29
@hexa:lossy.networkhexadang23:20:30
@hexa:lossy.networkhexa Lily Foster: looks like I'm not getting away without patching 🙂 23:20:41
@hexa:lossy.networkhexaalso … where is yallist suddenly coming from23:21:03
@lily:lily.flowersLily Fosterdamn, at least that's most of the way there23:21:06
@hexa:lossy.networkhexaoh, it is in the lock, so transitive dependecy23:21:18
@hexa:lossy.networkhexaindeed it is23:21:21
@lily:lily.flowersLily Foster
In reply to @hexa:lossy.network
also … where is yallist suddenly coming from
i mean idk, check the lockfile
23:21:24
@lily:lily.flowersLily Foster
In reply to @hexa:lossy.network
oh, it is in the lock, so transitive dependecy
yep
23:21:30
@hexa:lossy.networkhexa

pretix> npm WARN reify Removing non-directory /build/source/src/pretix/static.dist/node_prefix/node_modules

23:22:29
@hexa:lossy.networkhexaah lol23:22:30
@hexa:lossy.networkhexais it … in fact … deleting the symlink I created?23:22:38
@hexa:lossy.networkhexahow rude23:22:51
@lily:lily.flowersLily Foster yep that's now reification works. it adds and deletes 23:22:51
@lily:lily.flowersLily Fosterindeed23:22:54
@hexa:lossy.networkhexacopying it23:23:12
@lily:lily.flowersLily Foster
In reply to @lily:lily.flowers
yep that's now reification works. it adds and deletes
(well sort of. it doesn't necessarily delete without prune, but some things it does)
23:23:19
@hexa:lossy.networkhexa
pretix> running build
pretix> npm ERR! code EACCESdealTree: timing idealTree Completed in 156msms
pretix> npm ERR! syscall mkdir
pretix> npm ERR! path /build/source/src/pretix/static.dist/node_prefix/node_modules/fsevents
pretix> npm ERR! errno -13
pretix> npm ERR! Error: EACCES: permission denied, mkdir '/build/source/src/pretix/static.dist/node_prefix/node_modules/fsevents'
pretix> npm ERR!  [Error: EACCES: permission denied, mkdir '/build/source/src/pretix/static.dist/node_prefix/node_modules/fsevents'] {
pretix> npm ERR!   errno: -13,
pretix> npm ERR!   code: 'EACCES',
pretix> npm ERR!   syscall: 'mkdir',
pretix> npm ERR!   path: '/build/source/src/pretix/static.dist/node_prefix/node_modules/fsevents'
pretix> npm ERR! }
pretix> npm ERR! 
pretix> npm ERR! The operation was rejected by your operating system.
pretix> npm ERR! It is likely you do not have the permissions to access this file as the current user
pretix> npm ERR! 
pretix> npm ERR! If you believe this might be a permissions issue, please double-check the
pretix> npm ERR! permissions of the file and its containing directories, or try running
pretix> npm ERR! the command again as root/Administrator.
pretix> 
pretix> npm ERR! Log files were not written due to an error writing to the directory: /homeless-shelter/.npm/_logs
pretix> npm ERR! You can rerun the command with `--loglevel=verbose` to see the logs in your terminal
23:23:23
@hexa:lossy.networkhexano preserve mode possibly23:23:30
@lily:lily.flowersLily Fosteryeah probably23:23:40
@hexa:lossy.networkhexayep, that did it23:24:06

Show newer messages


Back to Room ListRoom Version: 6