Freffles
commented
1 day ago When I can eventually get into my existing project, I see this in my bolt terminal:
~/project
❯
~/project
❯ npx create-next-app@latest task-manager --typescript --eslint --yes && cd task-manager && npm install tailwindcss postcss autoprefixer && npx tailwindcss init -p
Need to install the following packages:
create-next-app@15.0.3
Ok to proceed? (y) y
Creating a new Next.js app in /home/project/task-manager.
Using npm.
Initializing project with template: app-tw
Installing dependencies:
- react
- react-dom
- next
Installing devDependencies:
- typescript
- @types/node
- @types/react
- @types/react-dom
- postcss
- tailwindcss
- eslint
- eslint-config-next
npm WARN deprecated inflight@1.0.6: 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 glob@7.2.3: Glob versions prior to v9 are no longer supported
npm WARN deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm WARN deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
npm WARN deprecated @humanwhocodes/config-array@0.13.0: Use @eslint/config-array instead
npm WARN deprecated eslint@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
added 375 packages in 19s
140 packages are looking for funding
run `npm fund` for details
Success! Created task-manager at /home/project/task-manager
^Cnpm install shadcn
^Cnpm run dev
~/project/task-manager 35s
❯ npm install shadcn
npm run dev
> task-manager@0.1.0 dev
> next dev
^Crm package-lock.json idealTree:task-manager: sill idealTree buildDeps
~/project/task-manager 1s
❯
~/project/task-manager
❯ npm install
~/project/task-manager 1s
❯
~/project/task-manager
❯ npm run dev
> task-manager@0.1.0 dev
> next dev
Downloading swc package @next/swc-wasm-nodejs... to /home/.cache/next-swc
up to date in 3s
140 packages are looking for funding
run `npm fund` for details
~/project/task-manager 3s
❯ ▲ Next.js 15.0.3
- Local: http://localhost:3000
✓ Starting...
✓ Ready in 2.9s
○ Compiling / ...
<w> [webpack.cache.PackFileCacheStrategy] Caching failed for pack: Error: Can't resolve 'tunnel-agent' in '/home/project/task-manager/node_modules/sharp'
<w> while resolving 'tunnel-agent' in /home/project/task-manager/node_modules/sharp to a directory
✓ Compiled / in 13.2s (642 modules)
GET / 200 in 13780ms
<w> [webpack.cache.PackFileCacheStrategy] Caching failed for pack: Error: Can't resolve 'tunnel-agent' in '/home/project/task-manager/node_modules/sharp'
<w> while resolving 'tunnel-agent' in /home/project/task-manager/node_modules/sharp to a directory
✓ Compiled in 721ms (294 modules)
<w> [webpack.cache.PackFileCacheStrategy] Caching failed for pack: Error: Can't resolve 'tunnel-agent' in '/home/project/task-manager/node_modules/sharp'
<w> while resolving 'tunnel-agent' in /home/project/task-manager/node_modules/sharp to a directory
Describe the bug
Windows 10: When I start the docker container with docker-compose --profile development up I get the following, when I load the localhost then there is additional info added. Seems like there is something happening behind the scenes and when it is finished I can reload the local host and it seems ok.
Assuming this was a docker issue, I have removed and reinstalled docker multiple times. I have updated node.js and have started with a clean repo (apart from my env file).
What is happening here and what can I do to resolve it?
Link to the Bolt URL that caused the error
n/a
Steps to reproduce
docker-compose --profile development up
Expected behavior
bolt would just start without needing additional dependencies to load
Screen Recording / Screenshot
No response
Platform
Additional context
No response