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

Support for v3.0? #1

Closed
robertstojs opened this issue May 30, 2022 · 3 comments
Closed

Support for v3.0? #1

robertstojs opened this issue May 30, 2022 · 3 comments

Comments

@robertstojs
Copy link

Getting the following:

warn - As of Tailwind CSS v2.2, `lightBlue` has been renamed to `sky`.
warn - Update your configuration file to silence this warning.

warn - As of Tailwind CSS v3.0, `warmGray` has been renamed to `stone`.
warn - Update your configuration file to silence this warning.

warn - As of Tailwind CSS v3.0, `trueGray` has been renamed to `neutral`.
warn - Update your configuration file to silence this warning.

warn - As of Tailwind CSS v3.0, `coolGray` has been renamed to `gray`.
warn - Update your configuration file to silence this warning.

warn - As of Tailwind CSS v3.0, `blueGray` has been renamed to `slate`.
warn - Update your configuration file to silence this warning.
wait  - compiling...
error - ./node_modules/next/dist/build/webpack/loaders/css-loader/src/index.js??ruleSet[1].rules[3].oneOf[8].use[1]!./node_modules/next/dist/build/webpack/loaders/postcss-loader/src/index.js??ruleSet[1].rules[3].oneOf[8].use[2]!./styles/globals.css
RangeError: Maximum call stack size exceeded
    at Array.map (<anonymous>)
wait  - compiling /_error (client and server)...
wait  - compiling...
error - ./node_modules/next/dist/build/webpack/loaders/css-loader/src/index.js??ruleSet[1].rules[3].oneOf[8].use[1]!./node_modules/next/dist/build/webpack/loaders/postcss-loader/src/index.js??ruleSet[1].rules[3].oneOf[8].use[2]!./styles/globals.css
RangeError: Maximum call stack size exceeded
    at Array.map (<anonymous>)

I hope to use this for my projects some day, thanks for starting this

@brandonmcconnell
Copy link
Owner

@robertstojs Thanks for opening this issue! I am currently working to resolve another issue that may be contributing to the error you're seeing, here: tailwindlabs/tailwindcss-intellisense#544

Once that's resolved, I'll also push a change for the color name warnings, so this should be fully compatible soon!

** In the meantime, you should be able to use version 1.1.0 which should resolve that error if it's related to using the tailwind-lerp-colors plugin (but not the warnings yet).

@brandonmcconnell
Copy link
Owner

@robertstojs I have reworked my plugin, and v1.1.4 should be stable and ready for use with Tailwind CSS v3.0+. This new version does bring about a paradigm shift in how tailwind-lerp-colors is initialized, so be sure to read the release notes for versions v1.1.3 and v1.1.4 and the updates top the README (file / diff).

I'd be excited to hear if you use this in your own project(s). Thanks again for your interest! 🙌🏼 🌮

@brandonmcconnell
Copy link
Owner

@robertstojs Closing this issue as resolved. If you encounter any further issues, please reach out. I'd love to help make this work for you! 😃

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