| /* eslint-disable global-require, import/no-extraneous-dependencies, @typescript-eslint/no-use-before-define */ | |
| /** | |
| * @see https://github.com/bcoe/c8/issues/376 | |
| * @see https://github.com/tapjs/processinfo/blob/33c72e547139630cde35a4126bb4575ad7157065/lib/register-coverage.cjs | |
| */ | |
| if (process.env.V8_COVERAGE) { | |
| process.setSourceMapsEnabled(true); | |
| const inspector = require('inspector'); | |
| const session = new inspector.Session(); |
⚠️ Warning: this document is out of date.For the most recent webpack5 instructions see MIGRATION.md.
Storybook 6.2 includes experimental Webpack 5 support. Webpack 5 brings a variety of performance improvements, as well as exciting new features like module federation. Here's a quick guide to get you going.
| // These methods and getter/setters force layout/reflow in Chrome/WebKit | |
| // From https://gist.github.com/paulirish/5d52fb081b3570c81e3a | |
| const getterSetters = [ | |
| 'offsetLeft', | |
| 'offsetTop', | |
| 'offsetWidth', | |
| 'offsetHeight', | |
| 'offsetParent', | |
| 'clientLeft', |
I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.
I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.
Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.