Skip to content
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

RFC: Turbopack support #114

Open
mxstbr opened this issue Jan 14, 2024 · 1 comment
Open

RFC: Turbopack support #114

mxstbr opened this issue Jan 14, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@mxstbr
Copy link
Contributor

mxstbr commented Jan 14, 2024

Summary

I tried next dev --turbo after running create-fuse-app and everything worked great—except the filesystem-based types/ folder isn't being picked up (as seen here because my types/Story.ts file isn't being picked up):

CleanShot 2024-01-14 at 11 16 06@2x

If I remove --turbo it works great:

CleanShot 2024-01-14 at 11 41 19@2x

Everything else seems to work!

@mxstbr mxstbr added the RFC A discussion about a future feature label Jan 14, 2024
@JoviDeCroock JoviDeCroock added bug Something isn't working and removed RFC A discussion about a future feature labels Jan 14, 2024
@JoviDeCroock
Copy link
Contributor

JoviDeCroock commented Jan 17, 2024

This is caused by turbopack being unable to resolve same-package imports, i.e. when we import fuse from fuse/client then it will assume that fuse does not exist or can't be resolved as it's not present in the package.json/node_modules of the sub-folder we are in. Instead what vite/webpack seem to do is either resolve it form the root or recognise that we are already on fuse.

The error is basically a side-effect from not being able to resolve the fuse import and hence having no schema available to the server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants