-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[turbopack] Unable to resolve any modules #4763
Comments
Are you using pnpm workspaces? We still need to document this, but you can add |
I updated to the latest version of turbo pack. The problem is now relegated to only errors with @ecominate/ui-common and @mui packages (related to the tsconfig |
Can you give us the result of running |
|
@jakeleventhal are you still experiencing this issue? |
yes
notably, tsconfig: {
"compilerOptions": {
"incremental": true,
"isolatedModules": true,
"noEmit": true,
"paths": {
// Required because minimal-ui contains multiple entry points
"@riptech/minimal-ui/*": ["../minimal-ui/src/*"],
// Use the MUI from minimal-ui
"@mui/*": ["../minimal-ui/node_modules/@mui/*"]
}
},
"exclude": ["dist", "node_modules"],
"extends": "@riptech/tsconfig/tsconfig.react.json",
"include": ["next-env.d.ts", "**/*.ts", "**/*.tsx"]
} the tsconfig being extended is: {
"compilerOptions": {
"allowJs": false,
"declaration": false,
"esModuleInterop": true,
"forceConsistentCasingInFileNames": true,
"jsx": "preserve",
"lib": ["dom", "ESNext"],
"module": "CommonJS",
"moduleResolution": "node",
"noEmitOnError": true,
"outDir": "./dist",
"inlineSources": true,
"resolveJsonModule": true,
"sourceRoot": "/",
"skipLibCheck": true,
"sourceMap": true,
"strict": true,
"target": "ES6"
},
"files": ["./declarations.d.ts"],
"extends": "./tsconfig.json",
"exclude": ["dist", "node_modules"]
} |
@jakeleventhal could you create a minimal repro in a public github repo or a codesandbox according to the bug template in the next.js repo? |
I am having the same issue with turbopack not resolving modules |
@ForsakenHarmony its going to require several hours of my time that I don't have to reproduce this (and potentially fail to do so). If you are willing, I can invite you to my team's repository to use that as a reproduction. |
In my case the problem was the following: I had:
In my Of course this overlaps with imports from node_modules that start with an I changed the import alias to |
I deeply second you on the "ugly everywhere" bit. I was very fond of using |
Going to close this issue as there is no full reproduction included that allows us to investigate further. Feel free to open a new issue if you're still running into problems please open a new issue so that we can investigate it. Thanks! |
What version of Next.js are you using Turbopack in?
13.3.1
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Mac
Describe the Bug
When I start my server, I get the following errors
It seems to not be able to resolve any modules
tsconfig below:
Expected Behavior
No errors :)
To Reproduce
Start server. I can help with private repo access privately if someone is able to help.
Reproduction Repo
No response
WEB-1043
The text was updated successfully, but these errors were encountered: