You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This error doesn't affect the working of skeleton, only the lsp complains.
Follow reproducing section, and an error like this will be raised by typescript server language server.
│ Cannot find module '@skeletonlabs/skeleton/plugin' or its corresponding type declarations. typescript (2307) [3, 26]
│ There are types at '/data/data/com.termux/files/home/teste-skeleton-next/node_modules/@skeletonlabs/skeleton/dist/plugin/index.d.ts', but this result could not be resolved under your current 'moduleResolution' setting. Consider updating to 'node16', 'nodenext', or 'bundler'.
Typescript language server version ❯ typescript-language-server --version 4.3.3
Haiz14
changed the title
LSP-SUGAR: typescript server raises skeleton module found but not resolved in tailwind.config.ts
LSP-SUGAR: typescript language server raises skeleton module found but not resolved in tailwind.config.ts
Oct 17, 2024
@Haiz14@Xenon27 I was able to replicate a similar issue last week when testing Skeleton for a Next.js project with Turbopack enabled. Can the two of you confirm which framework you're using.
SvelteKit | Next.js | other
If Next.js are you using Turbopack: Yes/No
EDIT Haiz I see you linked to the SvelteKit docs, so I'm going to assume this is what you were using. But I'll let you confirm.
Current Behavior
This error doesn't affect the working of skeleton, only the lsp complains.
Follow reproducing section, and an error like this will be raised by typescript server language server.
Typescript language server version
❯ typescript-language-server --version 4.3.3
Expected Behavior
LSP shouldn't raise this error.
Steps To Reproduce
tailwind.config.ts
should be something likeLink to Reproduction / Stackblitz
No response
More Information
tsconfig.json
'smodupeResolution
isbundler
The text was updated successfully, but these errors were encountered: