The super annoying thing here is that in my case it didn't manifest as a CSP failure but as a crash from the _website's_ code

Chrome is the opposite, adding inline scripts breaks stuff but its permissive about loading JS resources from Chrome extension URLs

Yeah I didn't manage to figure it out completely, based on the fix, it must be that when Firefox when it encounters a CSP with script-src, it wont allow loading from moz-extension://<extension-UUID>

Weirdly enough it doesnt mind you injecting an inline script (and fetch-ing the resource is allowed)

Replied on GH but that looks suspiciously similar to an issue I fixed on Alpine Devtools to do with how Firefox CSPs deal with extension resource URLs

As far as they're concerned, the website is only there to deflected from call center/other manned support channels

The only time reliability will come up & handling "edge cases" will be important is if there's some company wide initiative to reduce call center contact

I noticed this in an older version of date-fns (v1 or v2), 90% of the function I was reading was validating inputs, latest uses TS and doesnt validate as much

Before TypeScript and IDEs that understand TypeScript (even in JS), that was kind of the JS way of doing types... runtime validation

... in the gnarliest file of the project

1 line fix, but you had go know where to jam it

Decent

Jira and Confluence are enterprise kitchen sinks

As others mention, whatever you wanna build with them, you can.

Where smaller/earlier stages players are more focused/have less flexibility so enforce a simpler process.

Meanwhile Chrome rolled out Manifest v3 and started uninstalling non v3 extensions earlier this year...

👍 my pleasure

Also pre-TypeScript libraries that do a bunch of runtime parameter validation

If you prefer it to your email inbox, I'll be sending them out

Subscribe at buttondown.com/hugo#subscri...

Also found supademo.com/tools/screen...

To add annotations in the padding space to make the images pop a bit more

Aaaand just noticed it's not responsive

I've got a plan to move alpine.codewithhugo.com over (which is 11ty) so will likely redo at that point