-
Notifications
You must be signed in to change notification settings - Fork 262
Description
Describe the bug
❯ npx update
Need to install the following packages:
[email protected]
Ok to proceed? (y) y
npm warn deprecated [email protected]: This package is deprecated. Use require('node:util').isDeepStrictEqual instead.
npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
[15:11:45] using file ~/home/.npm/_npx/fed220c5d0a7c07e/node_modules/update/lib/updatefile.js
[15:11:45] starting update.default
[15:11:45] ✔ running: init
Current updaters: init
no updaters were saved.
[15:11:45] finished update.default ✔ 106ms
~/projects/sb1-flownqxb 7m 54s
❯ npm start
npm error Missing script: "start"
npm error
npm error Did you mean one of these?
npm error npm star # Mark your favorite packages
npm error npm stars # View packages marked as favorites
npm error
npm error To see a list of scripts, run:
npm error npm run
npm error A complete log of this run can be found in: /home/.npm/_logs/2025-08-28T09_42_34_540Z-debug-0.log
~/projects/sb1-flownqxb
❯ npm start
npm error Missing script: "start"
npm error
npm error Did you mean one of these?
npm error npm star # Mark your favorite packages
npm error npm stars # View packages marked as favorites
npm error
npm error To see a list of scripts, run:
npm error npm run
npm error A complete log of this run can be found in: /home/.npm/_logs/2025-08-28T09_43_13_120Z-debug-0.log
~/projects/sb1-flownqxb
❯
Link to the blitz that caused the error
https://stackblitz.com/edit/sb1-flownqxb?file=README.md
Steps to reproduce
terminal should be user friendly. actual application does not look that shown in preview.
Expected behavior
npm start must run Application
Parity with Local
- I have run the project in my local machine and I could not reproduce the issue.
Screenshots
No response
Platform
Browser name = Chrome
Full version = 139.0.0.0
Major version = 139
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36 Edg/139.0.0.0
performance.memory = {
"totalJSHeapSize": 79015028,
"usedJSHeapSize": 75189544,
"jsHeapSizeLimit": 2248146944
}
Hash = 96435430
Additional context
No response