Closed wmertens closed 2 months ago
Latest commit: 9e711520af9e33a346e05cc8f529fdb20bc1834e
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
npm i https://pkg.pr.new/@builder.io/qwik@6880
npm i https://pkg.pr.new/@builder.io/qwik-city@6880
npm i https://pkg.pr.new/eslint-plugin-qwik@6880
npm i https://pkg.pr.new/create-qwik@6880
commit: 9e71152
Name | Status | Preview | Last Commit |
---|---|---|---|
qwik-docs | ✅ Ready (View Log) | Visit Preview | 9e711520af9e33a346e05cc8f529fdb20bc1834e |
I like what Astro does in this case.
experimental: {
i18nDomains: true
},
An experimental object in the vite config that is typed
@thejackshelton I can do that too, but I prefer the shorter ['valibot', 'preventNavigate']
which doesn't need true
added. It's also typed BTW.
@thejackshelton I can do that too, but I prefer the shorter
['valibot', 'preventNavigate']
which doesn't needtrue
added. It's also typed BTW.
In that case something like:
experimental: ['valibot', 'preventNavigate']
works for me too as long as it's typed and autocompletes with the experimental thing to try out.
Great job @wmertens
I also think experimentalFeatures
is better than unstableFeatures
(if we're changing it, I suggest to change it across the entire PR)
awesome
Allow putting features behind feature flags
Starting with the
valibot
flag.