Headless installation during project refresh causes problems

Hello,

For the past few days I have been experiencing an annoying bug. Everytime a node project refreshes, it will perform a headless installation which will render the project inactive until the headless installation has completed.

I have tried fixing this issue with a multitude of potential solutions, which have not worked. They include:

  1. Enabling npm
  2. Enabling pnpm
  3. Reinstalling all of the dependencies
  4. Attempting to/updating pnpm/npm/node

This is what is being outputted every time the project is refreshed:

5:12 PM node v12.0.0, with pnpm
5:12 PM Installing...
5:12 PM Performing headless installation
5:12 PM
5:12 PM Total install time: 21804ms
1 Like

Hi there @Endzone - are you encountering this as you edit the app, or is it happening more than the every-12-hour-cycle that Glitch apps go through to make sure the containers are up to date?

If it’s happening as you’re editing, you may want to add a watch.json config file to exclude files from triggering the app restart - Can I change which files cause my app to restart? - Glitch Support

Hello @jenn,

Thank you for your reply! This happens whenever I need to restart my project, previously this would not happen at all and it would just refresh normally without having to install anything. A watch.json file helps a little bit but it is still rather annoying facing this issue, is there any way to get rid of the project having to install each restart?

This also pops up in the output in some occasions:

node v12.0.0, with pnpm
5:15 PM
Installing...
5:15 PM
 WARN  deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
5:15 PM
 WARN  deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
5:15 PM
Resolving: total 37, reused 4, downloaded 0
5:15 PM
Resolving: total 73, reused 32, downloaded 0
5:15 PM
Resolving: total 93, reused 63, downloaded 0
5:15 PM
Resolving: total 130, reused 98, downloaded 0
5:15 PM
Resolving: total 153, reused 133, downloaded 0
5:15 PM
Resolving: total 180, reused 156, downloaded 0
5:15 PM
Resolving: total 197, reused 183, downloaded 0
5:15 PM
 WARN  discord.js: prism-media@1.3.1 requires a peer of @discordjs/opus@^0.5.0 but none was installed.
5:15 PM
 WARN  discord.js: prism-media@1.3.1 requires a peer of ffmpeg-static@^4.2.7 || ^3.0.0 || ^2.4.0 but none was installed.
5:15 PM
 WARN  discord.js: prism-media@1.3.1 requires a peer of node-opus@^0.3.3 but none was installed.
5:15 PM
 WARN  discord.js: prism-media@1.3.1 requires a peer of opusscript@^0.0.8 but none was installed.
5:15 PM
 WARN  discord.js: ws@7.5.3 requires a peer of bufferutil@^4.0.1 but none was installed.
5:15 PM
 WARN  discord.js: ws@7.5.3 requires a peer of utf-8-validate@^5.0.2 but none was installed.
5:15 PM
Packages: +214
5:15 PM
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
5:15 PM
Resolving: total 212, reused 212, downloaded 0
5:15 PM
Resolving: total 212, reused 212, downloaded 0
5:15 PM
Resolving: total 212, reused 212, downloaded 0
5:15 PM
Resolving: total 212, reused 212, downloaded 0
5:15 PM
Resolving: total 212, reused 212, downloaded 0
5:15 PM
Resolving: total 212, reused 212, downloaded 0
5:15 PM
Resolving: total 212, reused 212, downloaded 0, done
5:15 PM
.../4.0.3/node_modules/bufferutil install$ node-gyp-build
5:15 PM
.../sqlite3/4.2.0/node_modules/sqlite3 install$ node-pre-gyp install --fallback-to-build
5:15 PM
.../5.0.5/node_modules/utf-8-validate install$ node-gyp-build
5:15 PM
.../4.0.3/node_modules/bufferutil install: Done
5:15 PM
.../sqlite3/4.2.0/node_modules/sqlite3 install: node-pre-gyp info it worked if it ends with ok
5:15 PM
.../5.0.5/node_modules/utf-8-validate install: Done
5:15 PM
.../sqlite3/4.2.0/node_modules/sqlite3 install: node-pre-gyp info using node-pre-gyp@0.11.0
5:15 PM
.../sqlite3/4.2.0/node_modules/sqlite3 install: node-pre-gyp info using node@12.0.0 | linux | x64
5:15 PM
.../sqlite3/4.2.0/node_modules/sqlite3 install: node-pre-gyp WARN Using request for node-pre-gyp https download 
5:15 PM
.../sqlite3/4.2.0/node_modules/sqlite3 install: node-pre-gyp info check checked for "/rbd/pnpm-volume/e8fd7458-2a7f-4849-beb9-01c63bfde6ec/node_modules/.registry.npmjs.org/sqlite3/4.2.0/node_modules/sqlite3/lib/binding/node-v72-linux-x64/node_sqlite3.node" (not found)
5:15 PM
.../sqlite3/4.2.0/node_modules/sqlite3 install: node-pre-gyp http GET https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v4.2.0/node-v72-linux-x64.tar.gz
5:15 PM
.../sqlite3/4.2.0/node_modules/sqlite3 install: node-pre-gyp http 200 https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v4.2.0/node-v72-linux-x64.tar.gz
5:15 PM
.../sqlite3/4.2.0/node_modules/sqlite3 install: node-pre-gyp info install unpacking node-v72-linux-x64/node_sqlite3.node
5:15 PM
.../sqlite3/4.2.0/node_modules/sqlite3 install: node-pre-gyp info tarball done parsing tarball
5:15 PM
.../sqlite3/4.2.0/node_modules/sqlite3 install: [sqlite3] Success: "/rbd/pnpm-volume/e8fd7458-2a7f-4849-beb9-01c63bfde6ec/node_modules/.registry.npmjs.org/sqlite3/4.2.0/node_modules/sqlite3/lib/binding/node-v72-linux-x64/node_sqlite3.node" is installed via remote
5:15 PM
.../sqlite3/4.2.0/node_modules/sqlite3 install: node-pre-gyp info ok 
5:15 PM
.../sqlite3/4.2.0/node_modules/sqlite3 install: Done
5:15 PM
.../4.8.6/node_modules/noblox.js postinstall$ node postinstall.js
5:15 PM
.../4.8.6/node_modules/noblox.js postinstall:               _     _             _     
5:15 PM
.../4.8.6/node_modules/noblox.js postinstall:              | |   | |           (_)    
5:15 PM
.../4.8.6/node_modules/noblox.js postinstall:   _ __   ___ | |__ | | _____  __  _ ___ 
5:15 PM
.../4.8.6/node_modules/noblox.js postinstall:  | '_ \ / _ \| '_ \| |/ _ \ \/ / | / __|
5:15 PM
.../4.8.6/node_modules/noblox.js postinstall:  | | | | (_) | |_) | | (_) >  < _| \__ \
5:15 PM
.../4.8.6/node_modules/noblox.js postinstall:  |_| |_|\___/|_.__/|_|\___/_/\_(_) |___/
5:15 PM
.../4.8.6/node_modules/noblox.js postinstall:                                 _/ |    
5:15 PM
.../4.8.6/node_modules/noblox.js postinstall:                                |__/     
5:15 PM
.../4.8.6/node_modules/noblox.js postinstall: Thank you for installing noblox.js.
5:15 PM
.../4.8.6/node_modules/noblox.js postinstall: Documentation: https://noblox.js.org/ 
5:15 PM
.../4.8.6/node_modules/noblox.js postinstall: GitHub: https://github.com/noblox/noblox.js
5:15 PM
.../4.8.6/node_modules/noblox.js postinstall: Support: https://discord.gg/R5GVSyTVGv
5:15 PM
.../4.8.6/node_modules/noblox.js postinstall: noblox.js is maintained with the help of its users but sometimes Roblox silently updates its API endpoints breaking noblox.js out of the blue.
5:15 PM
.../4.8.6/node_modules/noblox.js postinstall: We have created a request for Roblox to implement a change log to help keep the project's endpoints updated which you can find here: https://devforum.roblox.com/t/introduce-change-logs-to-roblox-api-endpoints/524783.
5:15 PM
.../4.8.6/node_modules/noblox.js postinstall: We also have our very own discord.js for support and informational purposes. To stay updated on new updates and bugs, you can join our Discord server with the following link: https://discord.gg/R5GVSyTVGv
5:15 PM
.../4.8.6/node_modules/noblox.js postinstall: Done
5:15 PM
5:15 PM
dependencies:
5:15 PM
+ @keyv/sqlite 2.0.2
5:15 PM
+ cheerio 0.22.0 (1.0.0-rc.10 is available)
5:15 PM
+ discord.js 12.5.3
5:15 PM
+ emoji-regex 9.2.2
5:15 PM
+ fs 0.0.2
5:15 PM
+ keyv 4.0.3
5:15 PM
+ moment 2.29.1
5:15 PM
+ ms 2.1.3
5:15 PM
+ noblox.js 4.8.6
5:15 PM
+ node-superfetch 0.2.3
5:15 PM
+ request 2.88.2 deprecated
5:15 PM
+ request-promise 4.2.6 deprecated
5:15 PM
5:15 PM
Total install time: 26602ms

Do you mind letting me know the name of the project - or if it’s private, can you email support@glitch.com (say Jenn sent you) with the name so I can have someone take a look?

Will do, thank you so much!

Edit: I just sent an email now - the subject is the title of this thread. Thanks again!

I would like to thank Jenn for their awesome efforts on assisting me to the best of their ability, I no longer face this issue as frequently. This issue can be considered resolved, thanks Jenn! :smiley:

1 Like