Guido Bouman

Update: I'm trying to fix this in the spec: https://github.com/w3c/csswg-drafts/issues/5123

Almost a year later: consensus is moving in the right direction. But no real decisions yet.

That's a good idea. Aside from the logging to the console, does the plugin do anything else you don't want it to? I'm wondering how this would work and what...

Hey hey, I can't view that repository it seems. Have you set that to private? Have you tried the React demo in the docs folder?

Do you not want to use https://github.com/ReactTraining/history ? The underlying history handler for react-router. Seems like that would take the issues out of routing, and focus on the actual value...

When you have a navigation guard that needs to stick on a part on the URL, no matter if it's a push or replace, this becomes very hard to do...

The `main.d.ts` does not seem to get picked up by `svelte-check`? 🤔 And inline data binds don't work. `let:data={myItem}` yields the following error:`Property 'key' does not exist on type 'unknown'.ts(2339)`....

@deemetree-at-satelligence https://github.com/Q42/hack-for-good/tree/main/web The Svelte project sits in a `web` folder. The `main.d.ts` file is next to the `main.ts` file. A run of `npm run validate` gives a lot of errors....

@danielkhan Any intentions for Sentry to put this on the roadmap somewhere soon? Right now we're building a separate lambda as per the workaround. But we have issues with Sentry...

As the Reporting API is not yet supported with the ingestion endpoints, we've created our own minimal endpoint in which we receive the reports and manually send that into Sentry...