github.com/antstanley/b...
Outstanding security fixes in flight vs what landed in 1.4.4
github.com/antstanley/b...
Outstanding security fixes in flight vs what landed in 1.4.4
✨ An updated polyfill for the new ext/uri features.
🔄 New type converters for URI components.
🔍 New extraction APIs for UriTemplate and URLPattern.
github.com/thephpleague...
#PHP #OSS #WebDevelopment #URI #URLPattern #URITemplate
✨ An updated polyfill for the new ext/uri features.
🔄 New type converters for URI components.
🔍 New extraction APIs for UriTemplate and URLPattern.
github.com/thephpleague...
#PHP #OSS #WebDevelopment #URI #URLPattern #URITemplate
https://www.razvantodica.com/blog/backend-tuesday-2026-10-13-77caf865
#CodeOnRoids #TuesdayPost #Urlpattern #ApiRouting
https://www.razvantodica.com/blog/backend-tuesday-2026-10-13-77caf865
#CodeOnRoids #TuesdayPost #Urlpattern #ApiRouting
Now preparing h3 and nitro upgrades, h3 v2 stable is next in the line 🤞
The routing toolkit powering h3 and Nitro.
rou3 now has over 80% URLPattern compatibility, with deliberate differences that keep server-side HTTP routing fast and sane.
Advanced patterns like /docs/**.md are now supported too.
Now preparing h3 and nitro upgrades, h3 v2 stable is next in the line 🤞
The routing toolkit powering h3 and Nitro.
rou3 now has over 80% URLPattern compatibility, with deliberate differences that keep server-side HTTP routing fast and sane.
Advanced patterns like /docs/**.md are now supported too.
The routing toolkit powering h3 and Nitro.
rou3 now has over 80% URLPattern compatibility, with deliberate differences that keep server-side HTTP routing fast and sane.
Advanced patterns like /docs/**.md are now supported too.
Zena has multiple runtime targets because the features can differ a lot: js, wasi, zena-cli, and default (plain core module).
Zena doesn't have a Node compat API, but the `js` target uses JS's strings, console, and soon regex, URL, and URLPattern.
Zena has multiple runtime targets because the features can differ a lot: js, wasi, zena-cli, and default (plain core module).
Zena doesn't have a Node compat API, but the `js` target uses JS's strings, console, and soon regex, URL, and URLPattern.
9) Ed Guloien (Mozilla) closes it out with Crates in Firefox over FFI: bringing the urlpattern crate into Gecko's C++ platform to ship a new Web API, and the joys of marshalling data across that boundary.
View ⚡️ talk on #rustconf schedule: rustconf2026.sched.com/event/2KIux
9) Ed Guloien (Mozilla) closes it out with Crates in Firefox over FFI: bringing the urlpattern crate into Gecko's C++ platform to ship a new Web API, and the joys of marshalling data across that boundary.
View ⚡️ talk on #rustconf schedule: rustconf2026.sched.com/event/2KIux
> Breaking: iframes and workers no longer load by default (restore with --load-resources iframe and --load-resources worker)
> New Web APIs inc URLPattern, navigator.geolocation and WorkerNavigator
More in comments
github.com/lightpanda-io/browser/releases/tag/0.4.0
> Breaking: iframes and workers no longer load by default (restore with --load-resources iframe and --load-resources worker)
> New Web APIs inc URLPattern, navigator.geolocation and WorkerNavigator
More in comments
github.com/lightpanda-io/browser/releases/tag/0.4.0
:root {
--home: url-pattern('/');
--detail: url-pattern('/detail/:id', 'https://example.com');
}
which would be the CSS-equivalent of:
const home = new URLPattern("home", window.location.href);
const detail = new URLPattern('/detail/:id', 'https://example.com');
:root {
--home: url-pattern('/');
--detail: url-pattern('/detail/:id', 'https://example.com');
}
which would be the CSS-equivalent of:
const home = new URLPattern("home", window.location.href);
const detail = new URLPattern('/detail/:id', 'https://example.com');
Although you could base it on JavaScript’s new URLPattern(urlStr, baseURLStr)
Although you could base it on JavaScript’s new URLPattern(urlStr, baseURLStr)
Still don't see it on pdsls though, unless I put it in as a URL pattern. No idea what's up with that.
I'm guessing you've applied/negated more than 1655 labels too. (that's as many as I can load with a * urlpattern)
Still don't see it on pdsls though, unless I put it in as a URL pattern. No idea what's up with that.
I'm guessing you've applied/negated more than 1655 labels too. (that's as many as I can load with a * urlpattern)
One thing we needed for Mastro across runtimes was URLPattern, another is stripTypeScriptTypes.
One thing we needed for Mastro across runtimes was URLPattern, another is stripTypeScriptTypes.
🔗 danholloran.me/posts/urlpat...
#webdev #javascript
🔗 danholloran.me/posts/urlpat...
#webdev #javascript
🔧 routeToRegExp() is now PCRE2-compatible
🔁 new regExpToRoute() to map proxy regexes back to rou3 patterns (URLPattern-ish)
✨ routesOverlap() / findOverlappingRoutes() built to handle complex logic like overlapping route rules in Nitro
🔧 routeToRegExp() is now PCRE2-compatible
🔁 new regExpToRoute() to map proxy regexes back to rou3 patterns (URLPattern-ish)
✨ routesOverlap() / findOverlappingRoutes() built to handle complex logic like overlapping route rules in Nitro
☑️ Newly available (from Sept 2025)
https://developer.mozilla.org/en-US/docs/Web/API/URLPattern/search
The search read-only property of the URLPattern interface is a string containing the pattern used to match the search part of a URL.
#webdev
☑️ Newly available (from Sept 2025)
https://developer.mozilla.org/en-US/docs/Web/API/URLPattern/search
The search read-only property of the URLPattern interface is a string containing the pattern used to match the search part of a URL.
#webdev
Did I miss a specificity part of URLPattern?
Did I miss a specificity part of URLPattern?
urllib.parse isn't WHATWG-conformant. So yarlpattern stands on yarl (the amazing WHATWG-flavored URL parser from the great folks at @aio-libs.org) and accepts yarl.URL directly.
urllib.parse isn't WHATWG-conformant. So yarlpattern stands on yarl (the amazing WHATWG-flavored URL parser from the great folks at @aio-libs.org) and accepts yarl.URL directly.