Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Move off of rollup and on to esbuild/swc/??? for generateSW
See original GitHub issueWe currently use Rollup in our build tools’ “generate” modes to take a templated service worker source file + config, and produce either a single output service worker (if inlineWorkbox is true) or a service worker + custom Workbox runtime bundle (if inlineWorkbox is false; this mode uses rollup-plugin-off-main-thread.
Rollup is a fantastic tool and we’ll likely continue to use it to generate, e.g., our pre-bundled libraries that are released on the CDN. For the more basic use case within the “generate” modes, it can be overkill, and its runtime performance is generally slower than Rust- or Go-based bundlers.
We should reevaluate our options for Workbox v7.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
No problem. New screenshots below.
Rollup:
Esbuild:
Yes. In fact I was also trying to bundle with swc, but stuck on inline import.