Igor Danchenko

There is one more related issue - ESLint is complaining about `beforeInteractive` being used outside of `pages/_document.js` (doh) > ./app/layout.tsx 31:17 Warning: `next/script`'s `beforeInteractive` strategy should not be used outside...

This issue is still present in the latest canary (13.4.7-canary.1) 1) Same styles are imported multiple times 2) The order of imports is not deterministic Here is a minimal repro...

@shuding, I appreciate you taking the time to look into this example. > it becomes very tricky if your CSS code itself has conflicts and some behaviors are undefined. I...

@slimshreydy, nice catch! Importing the named export indeed solves `clsx` issue. @andrewbranch, do you have any thoughts on why importing the default `clsx` export isn't working under `"moduleResolution": "NodeNext"`? ```...

@softcraft-development have you tried renaming your `.ts` files to `.mts`? Your package type is CommonJS, but you are using ESM syntax in `.ts` files - that's what probably confuses TypeScript...

@mhintzke chances are your source code module system contradicts your package module system and TypeScript file extensions. Here are the questions that will help you figure out the correct combination....

@mhintzke > Were you able to put skipLibCheck back to false at all? Yes, of course. But just keep in mind that TypeScript itself sets the `skipLibCheck` option to `true`...

@mhintzke your screenshot doesn't show the `"type": "module"` in your `package.json`. Can you confirm it's actually present? It would also be helpful if you could provide a minimal repro on...

@mhintzke I'm glad to hear you were able to identify your culprit. I took a quick look at `vitest-mock-extended` package.json and as far as I can tell, their module system...

> I am curious to see what @softcraft-development says as it will change whether or not this issue is still valid or not. It doesn't look like a valid issue...