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

build!: set vsce as a peer dependency #67

Merged
merged 1 commit into from
Jan 16, 2021
Merged

build!: set vsce as a peer dependency #67

merged 1 commit into from
Jan 16, 2021

Conversation

felipecrs
Copy link
Owner

@felipecrs felipecrs commented Jan 16, 2021

This is needed so the users can choose which vsce version to use. This is a breaking change because users who did not install vsce as a [dev]dependency and are not using npm@7 will have to install vsce manually.

This is needed so the users can choose which vsce version to use. This
is a breaking change because users who did not install vsce as a
[dev]dependency and [are not using npm@7](https://github.com/npm/rfcs/blob/latest/implemented/0025-install-peer-deps.md)
will have to install vsce manually.
@felipecrs felipecrs merged commit 23fec9e into master Jan 16, 2021
@felipecrs felipecrs deleted the vsce-peer-dep branch January 16, 2021 06:48
@raix
Copy link
Collaborator

raix commented Jan 16, 2021

🎉 This PR is included in version 4.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@felixfbecker
Copy link
Collaborator

What's the use case for choosing your own vsce version?

@felipecrs
Copy link
Owner Author

felipecrs commented Jan 16, 2021

@felixfbecker

  • upgrade it without having to upgrade here. Recently, vsce introduced automatic detection of yarn for example.

@felixfbecker
Copy link
Collaborator

vsce hasn't had a major version release since 2015, so consumers were always able to upgrade without needing to upgrade here and publishing a new version since we were using a floating version range - anyone can just npm update the package. So this seems like an unnecessary breaking change to me

@felipecrs
Copy link
Owner Author

felipecrs commented Jan 17, 2021

@felixfbecker You're right.

anyone can just npm update the package

Actually: npm install -D vsce@version-they-want, since it must be first added to the dependencies.

Do you think I should unpublish the 4.0.0?

felipecrs added a commit that referenced this pull request Jan 18, 2021
felipecrs added a commit that referenced this pull request Jan 18, 2021
felipecrs added a commit that referenced this pull request Jan 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants