Bug: Next.js configured with Turbopack cannot resolve Skeleton plugin import

[endigo9740]

Current Behavior

Next.js projects encounter a bug resolving the Skeleton plugin import when Turbopack is enabled.

Expected Behavior

The non-Turbopack version works as expected, so this should work when Turbopack is enabled.

Steps To Reproduce

1. Install Next.js per our recommendations: https://next.skeleton.dev/docs/get-started/installation/nextjs
2. Make sure to install Turbopack when prompted
3. Test the dev server - everything will work
4. Implement the Skeleton packages and Tailwind config
5. The dev server will throw an import related to the Plugin import in tailwind.config

Link to Reproduction / Stackblitz

No response

More Information

Next.js 15 is releasing this week, and there may be an uptick in users opting into the Turbopack setting for their projects.

[endigo9740]

@AdrianGonz97 FYI this seems like a similar error to what I experienced with Next.js. I've reached out to both users to confirm their framework here:

• LSP-SUGAR: typescript language server raises skeleton module found but not resolved in tailwind.config.ts #2877

But calling this out in case it's related and helps troubleshoot.