Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature?]: Provide a way to disable code splitting #1700

Open
2 tasks done
par5er opened this issue Dec 21, 2024 · 3 comments
Open
2 tasks done

[Feature?]: Provide a way to disable code splitting #1700

par5er opened this issue Dec 21, 2024 · 3 comments
Labels
enhancement New feature or request hold waiting for something to be addressed

Comments

@par5er
Copy link

par5er commented Dec 21, 2024

Duplicates

  • I have searched the existing issues

Latest version

  • I have tested the latest version

Summary 💡

An option in app.config.ts to disable code splitting. Only a single JS file would be emitted in this case instead of splitting on route.

Examples 🌈

No response

Motivation 🔦

I am mangling property names with terser but because every page has its own bundle, the property names are not consistent between chunks causing breakage

@par5er par5er added the enhancement New feature or request label Dec 21, 2024
@huseeiin
Copy link
Contributor

possible duplicate of #1575

@atilafassina
Copy link
Member

thanks for that @huseeiin . I agree there's a scenario where disabling lazy routes can be the same as serving a single-bundle.
But perhaps not necessarily. I see some usage/situations where not lazy-loading routes (or some routes) may not lead to everything in the same bundle.

but, @par5er we're currently revisiting our bundling architecture, so I'll put a hold on this one, I'm hoping in the future our configuration can be extensible enough that, perhaps, what you want can be entirely achieved in user-land.

@atilafassina atilafassina added the hold waiting for something to be addressed label Feb 13, 2025
@huseeiin
Copy link
Contributor

huseeiin commented Feb 13, 2025

thanks for that @huseeiin . I agree there's a scenario where disabling lazy routes can be the same as serving a single-bundle. But perhaps not necessarily. I see some usage/situations where not lazy-loading routes (or some routes) may not lead to everything in the same bundle.

but, @par5er we're currently revisiting our bundling architecture, so I'll put a hold on this one, I'm hoping in the future our configuration can be extensible enough that, perhaps, what you want can be entirely achieved in user-land.

ideally you'd choose whether to lazily or eagerly load each route

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request hold waiting for something to be addressed
Projects
None yet
Development

No branches or pull requests

3 participants