You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
flamescope (master @ be26595) ~> npm install
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
added 908 packages from 462 contributors in 14.683s
105 packages are looking for funding
run `npm fund` for details
flamescope (master @ be26595) ~> npm run webpack
> flamescope@0.3.0 webpack /tmp/dockerv/flamescope
> NODE_ENV=production webpack --mode production
[webpack-cli] SyntaxError: Invalid regular expression: /(\p{Uppercase_Letter}+|\p{Lowercase_Letter}|\d)(\p{Uppercase_Letter}+)/: Invalid escape
at pathToArgumentName (/tmp/dockerv/flamescope/node_modules/webpack/lib/cli.js:66:4)
at addFlag (/tmp/dockerv/flamescope/node_modules/webpack/lib/cli.js:170:16)
at traverse (/tmp/dockerv/flamescope/node_modules/webpack/lib/cli.js:243:21)
at traverse (/tmp/dockerv/flamescope/node_modules/webpack/lib/cli.js:299:23)
at traverse (/tmp/dockerv/flamescope/node_modules/webpack/lib/cli.js:248:24)
at Object.getArguments (/tmp/dockerv/flamescope/node_modules/webpack/lib/cli.js:308:2)
at WebpackCLI.getBuiltInOptions (/tmp/dockerv/flamescope/node_modules/webpack-cli/lib/webpack-cli.js:905:41)
at makeCommand (/tmp/dockerv/flamescope/node_modules/webpack-cli/lib/webpack-cli.js:1066:22)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:189:7)
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! flamescope@0.3.0 webpack: `NODE_ENV=production webpack --mode production`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the flamescope@0.3.0 webpack 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! /home/tanwang/.npm/_logs/2023-10-18T15_26_44_965Z-debug.log
@SinOverCos
That looks like a separate error that the project isn't building properly for you (although strangely it looks like it's an error in the webpack code), I'd open a separate issue about that
okay, I copy the app/public from https://github.com/Netflix/flamescope/tree/v0.2.0 to the master branch, it works. Consider it as a temporary workaround.
Hi! So I was able to get this to work. The dependencies in particular are just very out of date. I had to delete package-lock.json (and make sure node_modules is also deleted), then regenerate it with an npm install. Then npm run webpack should work and uv run run.py or whatever tool you're using for venv should work.
Activity
duarten commentedon Dec 16, 2022
You probably need to build the client:
zpget commentedon Dec 21, 2022
Error 500

Unknown mime type.
zpget commentedon Dec 21, 2022
GET /heatmap/?filename=perf.test01&type=perf&rows=50 HTTP/1.1" 500
node version v18.12.1
Updates readme to avoid Netflix#169
Desislav-Petrov commentedon Jan 28, 2023
Had the same issue (nothing at url) - the npm install commands fixed it, doing a PR to update the readme. Thanks for the suggested fix @zpget
akochepasov commentedon Feb 15, 2023
I had the same issue. Rinning
python run.pyresulted in the "Sorry, Nothing at this URL." error. Installingfixed it.
JSoet commentedon Sep 12, 2023
Caused by: #150
SinOverCos commentedon Oct 18, 2023
This doesn't quite fix it for me:
JSoet commentedon Oct 20, 2023
@SinOverCos
That looks like a separate error that the project isn't building properly for you (although strangely it looks like it's an error in the webpack code), I'd open a separate issue about that
GoodDayGeorge commentedon Oct 26, 2023
This also doesn't quite fix it for me:
Ubuntu 20.04.6 LTS nodejs v10.19.0
GoodDayGeorge commentedon Oct 26, 2023
okay, I copy the
app/publicfromhttps://github.com/Netflix/flamescope/tree/v0.2.0to themasterbranch, it works. Consider it as a temporary workaround.VorpalBlade commentedon Aug 10, 2025
The webpack command doesn't work, I get yet another error:
I'm not a js dev, so I have no idea what to do here.
computerquip-work commentedon Apr 27, 2026
Hi! So I was able to get this to work. The dependencies in particular are just very out of date. I had to delete package-lock.json (and make sure node_modules is also deleted), then regenerate it with an
npm install. Thennpm run webpackshould work anduv run run.pyor whatever tool you're using for venv should work.