Replies: 1 comment
-
Hello, The issue you're experiencing is unfortunately a known limitation of the current state of the Tailwind Play CDN setup. The use of Skypack, which has become outdated and lacks active maintenance, can cause compatibility problems for packages targeting modern JavaScript versions like ES2020 or later. Why This Happens: Tailwind Play's Dependency on Skypack: Potential Solutions: Ensure your package is compatible with ES2019 by adding appropriate build steps to transpile the output. Tools like Babel or SWC can help downgrade modern JavaScript to ES2019. esm.sh: A fast and maintained CDN that supports ES modules and modern builds. Submit Feedback to Tailwind Labs: Reach out to the Tailwind CSS team via their GitHub Issues page or Discord server to suggest migrating from Skypack to a maintained CDN like esm.sh. This kind of feedback helps inform their priorities. Are There Plans to Upgrade CDNs? If you’re comfortable advocating for change, consider opening an issue on Tailwind CSS’s GitHub or joining their community discussions to bring this to their attention. Best Regards |
Beta Was this translation helpful? Give feedback.
-
So I've been stuck trying to get my published package working on play.tailwindcss.com, as I can see it still uses the unmaintained skypack CDN, I can't seem to find the issue with my package not being able to get built by skypack, It seems it's been hardcoded to build only for "es2019" even though I'm adding the
?dist=es2020
query param for the CDN url..Are there any plans to upgrade to another CDN, like esm.sh or any other maintained ones..
Thanks
Edit:
Issue with skypack now is that [email protected] is breaking newer builds
Beta Was this translation helpful? Give feedback.
All reactions