D

Could this be because the custom library being used (base64url) is encoding strings without the base64 padding? ```ts btoa('User:10') // 'VXNlcjoxMA==' Buffer.from('User:10').toString('base64') // 'VXNlcjoxMA==' base64url.encode('User:10') // 'VXNlcjoxMA' ``` I'm only...

would this mean addressing the doubled references? https://github.com/freshgum-bubbles/typedi/issues/152 - then we could swap the dependency and we're done. Right now it would be a huge effort for us to go...

ChromeHeadless is now available, with support on it's way to karma-chrome-launcher: https://github.com/karma-runner/karma-chrome-launcher/pull/111 Would love to know how it performs in comparison to jsdom

ok my pull request should suffice. I realise it's failing on my project with lots of manifests, because I've not been pushing them to my project in a long time,...

still getting 500 errors :) not sure if possible to re-open? Projects with no manifests work again though I suppose

haven't really seen it said yet but, we're loading ROUTES async via a CMS like so (as recommended in standalone components guide): ```ts { provide: ROUTES, useFactory: () => {...

just out of curiosity, what's the problem with TSM? was thinking that it looked promising for some of our other projects

ESLint v9.0.0 is released too