Prod build appears stuck using latest release.

[nobicycle]

`[user@tower frontend]$ npm run build --verbose npm verb cli /usr/bin/node /usr/bin/npm npm info using [email protected] npm info using [email protected] npm verb title npm run build npm verb argv "run" "build" "--loglevel" "verbose" npm verb logfile logs-max:10 dir:/home/user/.npm/_logs/2024-03-02T06_04_12_481Z- npm verb logfile /home/user/.npm/_logs/2024-03-02T06_04_12_481Z-debug-0.log

build npm run build-wasm-prod && vite build || (npm run print-building-help && exit 1)

npm verb cli /usr/bin/node /usr/bin/npm npm info using [email protected] npm info using [email protected] npm verb title npm run build-wasm-prod npm verb argv "run" "build-wasm-prod" npm verb logfile logs-max:10 dir:/home/user/.npm/_logs/2024-03-02T06_04_12_851Z- npm verb logfile /home/user/.npm/_logs/2024-03-02T06_04_12_851Z-debug-0.log

build-wasm-prod wasm-pack build ./wasm --release --target=web`

No progress after 30 minutes.

System: $ uname -a Linux tower 6.6.16-2-MANJARO #1 SMP PREEMPT_DYNAMIC Sat Feb 10 09:40:02 UTC 2024 x86_64 GNU/Linux

[Keavon]

Hmmm. Did you install all the necessary documented prerequisites? Can you run a development build and serve from localhost?

[nobicycle]

@Keavon Yes, from the frontend folder, I did (without errors): $npm install

Changed 72 packages, and audited 399 packages in 11m

143 packages are looking for funding

$cargo install cargo-about

CPU is 0% utilisation for the wasm process. I added --verbose to the call of wasm in package.json but it made no difference.

The end of the log file just contains: 18 timing config:load:flatten Completed in 3ms 19 timing npm:load:mkdirpcache Completed in 0ms 20 timing npm:load:mkdirplogs Completed in 0ms 21 verbose title npm run build-wasm-prod 22 verbose argv "run" "build-wasm-prod" 23 timing npm:load:setTitle Completed in 1ms 24 timing npm:load:display Completed in 2ms 25 verbose logfile logs-max:10 dir:/home/user/.npm/_logs/2024-03-02T07_28_33_690Z- 26 verbose logfile /home/user/.npm/_logs/2024-03-02T07_28_33_690Z-debug-0.log 27 timing npm:load:logFile Completed in 10ms 28 timing npm:load:timers Completed in 0ms 29 timing npm:load:configScope Completed in 0ms 30 timing npm:load Completed in 59ms 31 silly logfile start cleaning logs, removing 1 files 32 silly logfile done cleaning log files

[0HyperCube]

After the build process, do you have a graphite/frontend/wasm/pkg containing a wasm file? Do you have a graphite/frontend/dist folder? Or perhaps a target/wasm32-unknown-unknown/release folder?

Could you elaborate on what you mean by the "wasm process"? Is this wasm-bindgen or rustc or your browser running the wasm? Furthermore can you reproduce this if you update rust, npm, etc, run a git clean -X -d -f and rebuild?