-
-
Notifications
You must be signed in to change notification settings - Fork 504
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
Proposed: Switch from path-to-regex to urlpattern-polyfill #1954
Comments
I think this is a great idea, since 11ty is still at a stage where such a switch is the least painful to adopt. Also I think that URLPattern is stable enough so we don't need to fear that it will change in the future in any significant way. I think 11ty should try to make as many open/upcoming breaking changes while upgrading to 1.0 as it can, so that 11ty can be stable after that. |
Blocked upstream by kenchris/urlpattern-polyfill#38 (local branch |
Alternatively, switch to https://github.com/pillarjs/path-to-regexp as a smoother transition step if Reasoning here is that |
Filed the above comment at #1988 and moved this one out of the 1.0 milestone. |
Officially, This issue is now for a migration from |
|
Milestoning this to 2.0 |
After further research I’m not sure Related: We currently rely on this from eleventy/src/Filters/ServerlessUrl.js Line 7 in 27f54aa
Related: |
De-milestoning from 2.0, sorry y’all! Re-adding to the enhancement queue.
|
Pre-1.0 status it might be awesome to attempt to switch the serverless URL matching code from https://www.npmjs.com/package/url-pattern to the future standard https://www.npmjs.com/package/urlpattern-polyfill
Documented at https://web.dev/urlpattern/
This will likely pay dividends later and keep us on the standards track for this feature.
Inspired by https://twitter.com/wanderview/status/1433535232268017665
The text was updated successfully, but these errors were encountered: