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

upgrade esbuild to 0.24 #553

Merged
merged 5 commits into from
Sep 24, 2024
Merged

upgrade esbuild to 0.24 #553

merged 5 commits into from
Sep 24, 2024

Conversation

floydspace
Copy link
Owner

  • migrate utils from fp-ts to effect

@floydspace floydspace merged commit 081242f into master Sep 24, 2024
3 of 4 checks passed
@floydspace floydspace deleted the feat/migrate-to-effect branch September 24, 2024 20:32
Copy link

🎉 This PR is included in version 1.54.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

},
"peerDependencies": {
"esbuild": ">=0.8 <0.24",
Copy link

Choose a reason for hiding this comment

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

Is there any reason to be limited to 0.24? The 0.25 is already up and I rather have a more loose peerDependecy

Copy link
Owner Author

Choose a reason for hiding this comment

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

Hey @ebisbe
the reason is to avoid issues due to possible breaking changes coming from next versions. it already happened.
Peer version indicates that it is tested with this versions range and should work. But no one stops you to use the latest esbuild version - in this case package manager will scream of course, which is a reminder to you, that it becomes your problem, if something does not work.
And I accept PRs if the peer version needs to be updated, but only if it is properly tested.

Copy link

Choose a reason for hiding this comment

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

Thanks for the explanation. I ( wrongly ) assumed that they were using semversionig. I'll try to make a PR.

Copy link
Owner Author

Choose a reason for hiding this comment

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

I believe they are using semver, but semver for v0 means: minor increment can be a breaking change

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.

2 participants