Tired of waiting for a release? Closure Compiler now publishes nightly builds to npm: npmjs.com/package/google….

At the close of 2018, almost all major browsers support Web Components and Shadow DOM. You know who still doesn't? LastPass and 1Password. Form elements in shadow dom might as well not exist for password managers.

Anybody know of a recipe for moving service worker cache items from an old cache version to a new one? When you have url versioned resources it seems logical to avoid downloading them again.

We are happy to announce our latest v5.5.0 release that comes with support for #ShadowDOM and allows you to easily traverse into your web components using WebDriver. Have a look at our new shadow$ and shadow$$ command webdriver.io/docs/api/eleme… #testAllTheThings /cc ️mush

For our team the three largest reductions in production facing issues came from adding the following to our workflow. 1. Adding compile-time type checking for all code. 2. Screenshot based UI testing. 3. Writing 1 end-to-end integration test that runs against staging nightly.

Why can we still not mutate cookies in a service worker? I want to offer a proper logout for my PWA while in offline mode which means deleting a HTTPOnly cookie. Setting a new cookie value on a manually constructed response should be allowed!

Why does almost every transpilation to JS framework target ES5 without type information and say it's "good enough".

Like presenting at conferences and interfacing with developers? We're hiring a Developer Advocate to help open up our API for banking. We support hundreds of US financial institutions and almost a million users every month (and growing). stackoverflow.com/jobs/272387

Want faster builds on windows? Closure Compiler now has a native binary for windows to match Linux and Mac OS. npmjs.com/package/google…

We are hiring!

We're hiring a Dev Advocate position to help us build our Banking as a Service platform: stackoverflow.com/jobs/387418/de… Also hiring Sr iOS engineers: stackoverflow.com/jobs/386489/sr…

Playing around with account linking and Google Assistant actions. Why on earth is PKCE for OAuth2 not supported? The draft OAuth 2.1 spec requires it.

With the upcoming end of 3rd party cookies I am seeing a rise in cookieless auth solutions particularly for framed content. These same apps rarely have content security policy. I forsee this going very badly.

After working on a large ES module project that runs 100% in a modern browser without a build first, switching to anything that requires a build step for development makes me groan.

Did you know that import maps can be used to solve the waterfall problem and improve caching for your PWA? Our apps are now shipping import maps to production to address this. banno.com/articles/impro…

Persisted Signals const count = persistedSignal(0, 'count') console.log(`page loaded ${++count.value} times`) codesandbox.io/s/preact-signa…

You can just ship things