| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
🦋 Changeset detectedLatest commit: 076d599 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Sorry, something went wrong.
| ], | ||
| ].filter(Boolean), | ||
| plugins: [ | ||
| require.resolve('@rschristian/babel-plugin-webpack-chunk-name-comments'), |
There was a problem hiding this comment.
Webpack is not able to provide names for chunks created with import(). This has two major implications:
So, I elected to solve this with a Babel plugin. It simply inserts a magic comment to specify the chunk name based upon the import path (import('./routes/foo.js') -> import(/* webpackChunkName: "routes-foo" */ "./routes-foo.js")). Source
The advantage of this approach is that users will not have to manually annotate their imports, we will not have to switch chunks to have named IDs1, we get file names that closely resemble previous output, and we keep named chunk groups.
Hopefully it's not an issue adding my own module. It's quite simple and I'm happy to maintain it if there are any issues.
Sorry, something went wrong.
| 'es-polyfills.legacy.js': 42690, | ||
| 'dom-polyfills.8a933.legacy.js': 5252, | ||
| 'dom-polyfills.8a933.legacy.js.map': 18836, | ||
| 'es-polyfills.legacy.js': 61323, |
There was a problem hiding this comment.
Note to self: 20kb jump seems quite heavy. Thinking something isn't right.
Sorry, something went wrong.
* feat: webpack-v5 * test: Update tests * docs: Updating docs to reflect changes * chore: Removing optimize-plugin local patch
* refactor: Determine CSS module by filename, not directory * docs: Adding changeset * refactor: Project creation pull from templates 'main' branch * test: Updating tests * revert: Accidentally removed log message
* refactor: Extracting out project creation to own package * docs: Adding changeset * refactor: Misc edits to common deps & workspace helper scripts * test: Fixing 'create' test suite * ci: Increase minimum Node version * chore: Fix typos * docs: Update ReadMe instructions * chore: Better (and untaken) package name * docs: Update changeset * test: Update 'create' test suite & build output hashes * docs: Expounding upon changeset
* refactor: Drops support for Preact v8 * docs: Adding changeset
* refactor: Switch over to automatic runtime transform for JSX * test: Removing `h` imports from test suite * docs: Adding changeset
* docs: Adding readme for create-cli * feat: Initial publish * fix: Correcting broken readme links
* refactor: Disable hashing ssr-build's css * docs: Adding changeset * test: Fix unrelated change from altered template
* refactor: Separate internal concepts of config and env * docs: Adding changeset
* refactor: Revise inconsistent, unused, and deprecated flags * docs: Adding changeset
* refactor: Better root error handling * refactor: Switch prerender plugin to be async for error gen * refactor: Simplify & improve compilation messages
…isc housekeeping (#1753) * refactor: Drop rimraf for built-in fs.rm * refactor: Drop src argument in build & watch cmds * refactor: Extract info cmd from CLI entrypoint * refactor: Remove update-notifier * refactor: Switch from fs.promises to fs/promises * docs: Adding changeset
* refactor: Merging EJS templates and switcing preferred template extension to .ejs * test: Fixing test suite to reflect latest changes * chore: Cleaning * docs: Updating ReadMe * docs: Adding changeset * refactor: Add error message for <% preact.(head|body)End %>
* refactor: Enables HMR via Prefresh by default * docs: Adding changeset * test: Updating tests to reflect changes to templates
* refactor: Remove Critters (perhaps temporarily) * docs: Adding changeset
| Back | FazBrowse Home | New Git URL |
What kind of change does this PR introduce?
Experimental refactor
Did you add tests for your changes?
Yes
Summary
Deprecates async-loader and automatic route splitting for instead relying on lazy loading, like with preact-iso's lazy().
Code splitting as it previously worked was quite opaque, relying on magic directory names rather than user code.
This should make bundle splitting much more transparent by moving the control into user code.
Does this PR introduce a breaking change?
Yes