Code splitting support
See original GitHub issueIf you turn on experimentalCodeSplitting
, this plugin doesn’t log anything. With single file input/output, the plugin works fine.
Issue Analytics
- State:
- Created 5 years ago
- Comments:15 (9 by maintainers)
Top Results From Across the Web
Code Splitting - webpack
This feature allows you to split your code into various bundles which can then be loaded on demand or in parallel. It can...
Read more >Code-Splitting - React
Code -splitting your app can help you “lazy-load” just the things that are currently needed by the user, which can dramatically improve the...
Read more >Code Splitting | Create React App
This project setup supports code splitting via dynamic import() . Its proposal is in stage 4. The import() function-like form takes the ...
Read more >Code splitting - MDN Web Docs Glossary
Code splitting is a feature supported by bundlers like Webpack and Browserify which can create multiple bundles that can be dynamically ...
Read more >Reduce JavaScript payloads with code splitting - web.dev
Code splitting is a technique that seeks to minimize startup time. When we ship less JavaScript at startup, we can get applications to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry for the delay on this, I’m having difficulty getting it resolved 😕 Still trying to figure it out though, will let you know as I figure anything out on it.
On the test, I suppose it could be something to do with line-endings depending on how you have git setup. Testing based on output bytes isn’t probably for the best due to issues like that or minor changes in Rollup potentially causing a single byte difference will result in failures. I’ll find a better way to test those.
In the interim based on the output you got it is working, the failure is superficial so you can change the expected bytes in your fork to match. It’s on line 182 -> size property. You may also have to change the other as well.
Given this flag is deprecated and is now the default behavior and it does provide output now (but outputs more than once, which is noted in the readme) I’m going to close this. That said, if the outputting more than once deems need to open a separate issue to consolidate the output feel free to open one for that.