Stuck on an issue?

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.

modern only build

See original GitHub issue

What problem does this feature solve?

Allows to create modern only build. Some applications don’t need legacy build. I guess that could be achieved by proper configuration of browsersrc file, but this solution seems a bit hacky and unintuitive, and I’m not sure if it would work

What does the proposed API look like?

For example vue-cli-service build --modern="only" vue-cli-service build --modern --no-legacy vue-cli-service build --modern-only

Issue Analytics

State:
Created 4 years ago
Reactions:38
Comments:21 (1 by maintainers)

Top GitHub Comments

14reactions

alexcrooxcommented, May 13, 2020

I would like a flag to disable legacy build so I can run both the legacy and modern builds in parallel in my continuous integration/deployment environment. This would help speed up deployments, and overcome challenges where enforced RAM limits are hit in containers when trying to build both modern and legacy at the same time.

13reactions

AceLingcommented, Feb 17, 2022

First, modify .browserslistrc:

> 1%
last 2 versions
not dead
not ie 11

Then, execute npm run build and CMD output:

All browser targets in the browserslist configuration have supported ES module. Therefore we don’t build two separate bundles for differential loading.

Finally, I get “modern only build”!!!