e2e test: Running next start after build has issues
Unanswered
Bonaparte's Gull posted this in #help-forum
Bonaparte's GullOP
No CSS or JS is loaded when running
This is happening locally and in ci (github action).
I'm having to run my tests in
After two days of debugging my e2e test i've realised they are failing due to next start being broken
next start after a successful next build This is happening locally and in ci (github action).
I'm having to run my tests in
dev mode to ensure the css/js files are loaded. Not ideal! After two days of debugging my e2e test i've realised they are failing due to next start being broken
33 Replies
Bonaparte's GullOP
latest version of next
mono repo
pages directory
mono repo
pages directory
@Bonaparte's Gull No CSS or JS is loaded when running `next start` after a successful `next build`
This is happening locally and in ci (github action).
I'm having to run my tests in `dev` mode to ensure the css/js files are loaded. Not ideal!
After two days of debugging my e2e test i've realised they are failing due to next start being broken
No CSS or JS is loaded when running next start after a successful next buildthis is weird, give us a minimal example because this shouldn't happen
Bonaparte's GullOP
i couldn't replicate it using a fresh project (npx create-next-app@latest)
My project is a mono repo with 3 nextjs apps (apps/cards -port 4000, apps/links - port 3333, apps/platform - port 3000)
My project is a mono repo with 3 nextjs apps (apps/cards -port 4000, apps/links - port 3333, apps/platform - port 3000)
It's a private project so I can't really share it.
i'll try making a mono repo example
i'll try making a mono repo example
The difficulty to replicate is precisely why I need a minimal example, as otherwise I cannot debug what is wrong
Bonaparte's GullOP
absolutely, i'll try and knock up a minimal example
rather than creating an example, could i invite you to the repo on git?
actually/.. scrap that... i'll try and reproduce it with a minimal example
Bonaparte's GullOP
arse! haven't been able to produce a minimal reproduction
Bonaparte's GullOP
FYI: issues seems to have been introduced by 13.4.13
i appreciate you can't really do much without an example
i appreciate you can't really do much without an example
13.4.12 works as expected
hmm i haven't upgraded to 13.4.13 because it has a new bug that directly affects my apps
so even if you give me an example idt i can help
Bonaparte's GullOP
nice! what is the bug?
but if 13.4.12 works, time to pin dependency to 13.4.12
@Bonaparte's Gull nice! what is the bug?
lucide-react just breaks completely in 13.4.13
Bonaparte's GullOP
bloody 'ell
app directory?
yeah
Bonaparte's GullOP
eee... yah, i can't see myself using that for a few years!
things become very messy, they did something with modularizeImports that looked clever but just broke everything related to lucide-react
and despite warnings they still continued to release that
tbf i'm just really disappointed at the direction of the app router recently
Bonaparte's GullOP
absolutely... the app router stuff just sounds like a f**king nightmare
TBH, i'm getting increasingly fed up with react... if it weren't for things like zustand and tanstack I would have jumped ship to svelte or solid.
yeah makes sense, i haven't used solid but svelte is such fun to use
but react pays the bills, something svelte can barely do
so what to do
Bonaparte's GullOP
drink beer!!
good idea!
Bonaparte's GullOP
2.5 days later
all because of the latest next release
madness!