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

Cannot find package '@ianvs/prettier-plugin-sort-imports' #314

Open
SerenModz21 opened this issue Aug 25, 2024 · 1 comment
Open

Cannot find package '@ianvs/prettier-plugin-sort-imports' #314

SerenModz21 opened this issue Aug 25, 2024 · 1 comment

Comments

@SerenModz21
Copy link

SerenModz21 commented Aug 25, 2024

What version of prettier-plugin-tailwindcss are you using?

0.6.6

What version of Tailwind CSS are you using?

3.4.10

What version of Node.js are you using?

20.17.0

What package manager are you using?

Yarn v4.4.1

What operating system are you using?

Windows

Reproduction URL

I don't have a specific reproduction URL but multiple repos that experience this issue. One of those that is public is my website's repo: https://github.com/SerenModz21/serenmodz.rocks

If using my website's repo to reproduce the issue, the tailwind prettier plugin will need to be set back to ^0.6.6 because I have downgraded it for now, until something can be resolved.

After changing the version to the above, run yarn followed by yarn format and the error will be shown.

Describe your issue

When trying to format with the latest version, the following error is shown:

❯ yarn format
[error] Cannot find package '@ianvs/prettier-plugin-sort-imports' imported from [redacted]\serenmodz.rocks\node_modules\prettier-plugin-tailwindcss\dist\index.mjs
[error] Did you mean to import "@ianvs/prettier-plugin-sort-imports/lib/src/index.js"?

While I understand the "cannot find package" is due to me not having @ianvs/prettier-plugin-sort-imports installed, we're not required to need it and I don't want to sort my imports, just tailwind classes.

As mentioned above, I have decided to downgrade back to 0.6.5 until this has been resolved.

@felixdorn
Copy link

Downgrading to 0.6.5 fixes the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants