dev server exits when compiling without output - please help
Unanswered
Argente Brun posted this in #help-forum
Argente BrunOP
I've updated to Next1 5, and now when i run
Using
Using
Increasing memory limit does nothing
It only affects Turbopack - but I can't use webpack because of another bug
It does work when I disable a Tailwind plugin, but it also works when I leave that in and remove a bunch of imports from
I can't reproduce the issue with a fresh next install
Not using docker
Please send help
npm run dev, then open the app in my browser, it logs that it's compiling the route then exits with code 0 without any output.Using
--inspect complains that the port is already in use 3 times (which it isn't before running npm run dev)Using
--trace-exit provides nothingIncreasing memory limit does nothing
It only affects Turbopack - but I can't use webpack because of another bug
It does work when I disable a Tailwind plugin, but it also works when I leave that in and remove a bunch of imports from
page.tsx - suggests memory is the problem? I can't reproduce the issue with a fresh next install
Not using docker
Please send help
8 Replies
Argente BrunOP
can u try disabling the debugger and see if that helps?
before v15 migration, was it working?
seems like its stuck on compiling your dynamic route
do you do some unusual things in layout.tsx or page.tsx?
Argente BrunOP
It was working before v15 yep, nothing unusual in layout.tsx or page.tsx
I've narrowed it down now to the Preline Tailwind plugin.
I have a utility module which resolves the Tailwind config so that the
If I comment out Preline from plugins in the TW config, it works.
It seems that whenever
I've narrowed it down now to the Preline Tailwind plugin.
I have a utility module which resolves the Tailwind config so that the
screen breakpoints can be reusedimport resolveConfig from 'tailwindcss/resolveConfig';
import baseTailwindConfig from '@/../tailwind.config';
export const tailwindScreens = resolveConfig(baseTailwindConfig).theme.screens as Record<
'sm' | 'md' | 'lg' | 'xl' | '2xl' | '3xl' | '4xl',
string
>;If I comment out Preline from plugins in the TW config, it works.
It seems that whenever
baseTailwindConfig is read, it breaks. So if I comment out the resolveConfig line, it no longer breaks. If I add console.log(typeof baseTailwindConfig), it breaks.Argente BrunOP
Opened an issue: https://github.com/vercel/next.js/issues/72997