Closed icflorescu closed 1 year ago
@icflorescu This is most likely because we're now testing in a monorepo-dependent environment; I'll try to troubleshoot this issue and release a new version as soon as possible within 24h.
We already have a complete process for the Svelte example, but the official guide has not been completed yet, so stay tuned.
@icflorescu You can first try adding "type":"module"
to package.json to see if it works. https://github.com/master-co/css/blob/beta/examples/svelte-with-progressive-rendering/package.json#L24
My package.json
already has "type": "module"
, as SvelteKit only works with esm.
As stated in the reproduction steps above, I actually copied the svelte-with-progressive-rendering
example you mentioned.
I realized the official guide was a bit outdated, that's why I went straight to the example in the repo.
I'll stick with 2.0.0-beta.119
for the moment.
Thanks for looking into it. I'll keep an eye on the progress.
As I already mentioned, I think you're doing an awesome job with Master CSS 👍 I'm an old-timer and the author of a few open-source projects myself (including Mantine DataTable and tRPC-SvelteKit), but to be honest I couldn't connect to the latest TailwindCSS hype, mostly due to the fact building useful UI libraries without making use of dynamic styles is very difficult.
The way I see things, Master CSS will be able to change that, due to its fast JIT/Progressive/Hybrid rendering; that's why it caught my attention. So, keep up the good work! 😁
⚠️ This version still has issues, please wait for the next version @master/css@beta.129
:tada: This issue has been resolved in version 2.0.0-beta.128 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
@icflorescu Sorry; I'm in a daze and didn't notice you were using the official example. 😅
It feels like you're an experienced player, and your reproduction can almost be used as a quick start section of our official guide. 😍
Errors in the last few versions may be related to the tree-shakable package I improved a while ago, and I finally fixed it after a whole night of tossing.
npm i @master/css@beta
again → https://github.com/master-co/css/releases/tag/v2.0.0-beta.129
That was quick!
:tada: This issue has been resolved in version 2.0.0-rc.1 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Description
Trying to:
in a Svelte
hooks.server.js
file results in an error.This gets logged in the console:
And this in the browser:
I was persistent enough to try it with different
@master/css
versions and managed to determine that2.0.0-beta.119
works fine and the error happens starting withbeta > 120
(including the latest127
).Most likely something changed in the building workflow at that point in time.
Reproduction
@master/css
beta are correctly installed:@master/css@beta.119
:Thank you for creating
@master/css
🙏 I can't wait to give it a try with SvelteKit :-)System Informations
This should be irrelevant:
Browser: Brave/Chromium 111 OS: Arch/Manjaro Linux 22 Node.js: 18.15.0 Package Manager: npm 9.6.2