fix(postcss-preset-env): client side polyfills #3051
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "dpschen/frontend:fix-postcss-preset-env-client-side-polyfills"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@ -69,0 +71,4 @@
// get a better browser support:
// https://github.com/csstools/postcss-plugins/tree/main/plugin-packs/postcss-preset-env#plugins-that-need-client-library
// see also './src/polyfills.ts'
enableClientSidePolyfills: true,
Now that I enabled the former default again, I'm unsure if I would need to disable the other plugins again as well.
Maybe it's also enough to do the opposite: force enable the focus-visible-pseudo-class plugin like this:
AFAIK 'focus-visible-pseudo-class' is the only feature of those plugins that require a client side polyfill that we use.
When I read the documentation of that plugin I get a bit confused though if we even need that
src/polyfills.ts
file or if enabling that plugin should be enought for the client side polyfill to be included. See that sentence:Source: https://github.com/csstools/postcss-plugins/tree/main/plugins/postcss-focus-within#browser
Really confusing that documentation!
If it's possible to enable the polyfill only for that specific feature I think that's a good idea. Or is the rest tree-shaked?
That sounds like it does not need a polyfill at all? (When targeting newer browsers than these)
I'm unsure.
It's also very time-consuming to test this since I would need to pick a browser version in browserslist that doesn't support those features natively.
Should I try the variant where I only enable features?
If that's easier, please do.
Done. Please re-review
Hi dpschen!
Thank you for creating a PR!
I've deployed the changes of this PR on a preview environment under this URL: https://3051-fix-postcss-preset-env-client-si--vikunja-frontend-preview.netlify.app
You can use this url to view the changes live and test them out.
You will need to manually connect this to an api running somehwere. The easiest to use is https://try.vikunja.io/.
Have a nice day!
7364b790ca
to29e306841c