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

feat: legacy options to revert to v2 strategies #8623

Merged
merged 14 commits into from Jun 17, 2022

Conversation

patak-dev
Copy link
Member

@patak-dev patak-dev commented Jun 16, 2022

Description

Add new options marked as experimental and deprecated to revert to v2 strategies, and express clear intent that these may be removed in a v3 minor

  • legacy.devDepsScanner
  • legacy.buildRollupPluginCommonjs
  • legacy.buildSsrCjsExternalHeuristics

What is the purpose of this pull request?

  • Bug fix
  • New Feature
  • Documentation update
  • Other

@patak-dev patak-dev changed the title fix: allow cache overlap in parallel builds feat: experimental options to revert to v2 strategies Jun 16, 2022
@patak-dev patak-dev added the p3-significant High priority enhancement (priority) label Jun 16, 2022
Copy link
Member

@bluwy bluwy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like we might need new docs for the experimental options. And also, perhaps we should deprecate build.commonjsOptions too?

docs/guide/migration.md Outdated Show resolved Hide resolved
docs/guide/migration.md Outdated Show resolved Hide resolved
docs/guide/migration.md Outdated Show resolved Hide resolved
@antfu
Copy link
Member

antfu commented Jun 17, 2022

experimental feel a bit future-oriented to me. Maybe we could introduce them as legacy. or compact.?

@patak-dev patak-dev changed the title feat: experimental options to revert to v2 strategies feat: legacy options to revert to v2 strategies Jun 17, 2022
@patak-dev
Copy link
Member Author

Thanks @antfu, legacy sounds a lot better to me. Changed the PR to use it 👍🏼
I still marked these three options as @experimental so we can break semver in a future minor removing them without breaking the contract for Vite itself.

docs/guide/migration.md Outdated Show resolved Hide resolved
docs/guide/migration.md Outdated Show resolved Hide resolved
patak-dev and others added 3 commits June 17, 2022 12:22
Co-authored-by: 翠 / green <green@sapphi.red>
Co-authored-by: 翠 / green <green@sapphi.red>
docs/guide/migration.md Outdated Show resolved Hide resolved
Co-authored-by: 翠 / green <green@sapphi.red>
sapphi-red
sapphi-red previously approved these changes Jun 17, 2022
Copy link
Member

@sapphi-red sapphi-red left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One typo and diff is including #8592 for some reason but LGTM

docs/guide/migration.md Outdated Show resolved Hide resolved
Co-authored-by: 翠 / green <green@sapphi.red>
@patak-dev patak-dev merged commit 993b842 into main Jun 17, 2022
@patak-dev patak-dev deleted the feat/deprecate-commonjs-plugin branch June 17, 2022 18:58
@sapphi-red sapphi-red mentioned this pull request Jun 19, 2022
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p3-significant High priority enhancement (priority)
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

4 participants