-
-
Notifications
You must be signed in to change notification settings - Fork 272
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
tailwindcss
Has an oxide
Error
#2553
Comments
Hi @shellscape can you share the steps a little please. The |
The steps, as it were, are simply to import tailwind via jspm's CDN. You'll see the error as the oxide package isn't something that exists, and it's something tailwind uses internally as a janky A/B |
@shellscape jspm.dev will be deprecated soon, is what @JayaKrishnaNamburu is referring to. Instead we are all in on import maps at this point. For example, here is a tailwind-generated import map - https://generator.jspm.io/#U2NhYGBkDM0rySzJSU1hKEnMzCnPzEtxMNEz0DMAADgbhBYdAA. As you can see though it's kinda pulling in the world.... what is it doing!? Running that via the "Sandbox" link gives a different error to the one you posted. Would be nice to get to the bottom of this for sure. How does one usually run tailwind in the browser? |
The
tailwindcss
mapping has an error that prevents using the CDN for loading. See: https://jspm.dev/tailwindAt some point during import map generation,
https://jspm.dev/npm:@tailwindcss/oxide!cjs
is set, and when requested:Not sure what else to report. Was attempting to use this during a Vite build and ran across this. Apologies if this is the wrong project, all the sites default the Github link to here.
The text was updated successfully, but these errors were encountered: