Skip to content

feat: migrate to TypeScript and support TailwindCSS v4 #385

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

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

ImBIOS
Copy link

@ImBIOS ImBIOS commented Jan 24, 2025

feat: migrate to TypeScript and restructure project files

Description

Preparation to support TailwindCSS v4 requires me to migrate it to TS to protect my sane and peaceful mind

Fixes #384
Fixes #325

Related:

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
Please also list any relevant details for your test configuration

  • Test A
  • Test B

Test Configuration:

  • OS + version: e.g. macOS Mojave
  • NPM version: ...
  • Node version: ...

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • Any dependent changes have been merged and published in downstream modules
  • I have checked my code and corrected any misspellings

Preparation to support TailwindCSS v4 requires me to migrate it to TS to protect my sane and peaceful mind
@ImBIOS ImBIOS changed the title [DRAFT] feat: migrate to TypeScript and restructure project files feat: migrate to TypeScript and restructure project files Jan 24, 2025
@ImBIOS ImBIOS mentioned this pull request Jan 24, 2025
@ImBIOS ImBIOS closed this Jan 24, 2025
@ImBIOS ImBIOS reopened this Jan 24, 2025
@ImBIOS ImBIOS changed the title feat: migrate to TypeScript and restructure project files feat: migrate to TypeScript and support TailwindCSS v4 Jan 24, 2025
@ImBIOS
Copy link
Author

ImBIOS commented Jan 24, 2025

Please guys,
If you guys want to support me, I don't like the idea of financial donations while I'm still a healthy young man, just hire me or tell someone to hire me.

we're only going to include `lib` in the npm packages, not the git repo
@CHC383
Copy link

CHC383 commented Jan 25, 2025

I think the v4 branch is https://github.com/francoismassart/eslint-plugin-tailwindcss/tree/alpha/v4-basic-files

@Pnlvfx
Copy link

Pnlvfx commented Feb 17, 2025

Can you show how to use it inside the eslint flat config?

@drake-nathan
Copy link

Amazing work. Any chance this will be merged soon? Anything I can help with?

},
"dependencies": {
"@typescript-eslint/utils": "^7.13.0",
"eslint": "^8.56.0",
Copy link

@drake-nathan drake-nathan Mar 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

eslint should be a peer dep, right?

@Jean-Dum
Copy link

Jean-Dum commented Apr 4, 2025

Thanks for this great work! Any news about this PR?

@brandanking-decently
Copy link

@ImBIOS do you know if this will get merged soon? If not do you think you could create your own NPM package for people to use in the mean time?

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

Successfully merging this pull request may close these issues.

[Feature request] Support for Tailwind v.4.0.0 [Feature request] Support Tailwind 4
6 participants