-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
BREAKING CHANGE: drop core-js from dependencies which the app should be responsible for #31
Conversation
@rxmarbles what do you think? Also I'd like to move this package to react-dropzone org. Thoughts? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@okonet seems reasonable to me. also this repo seems to already be in the react-dropzone
org. Do you mean to move this code into react-dropzone
directly?
I moved the repo to the org after I mentioned it. Feel free to move the code along but in this case we might want to create a monorepo structure to accommodate other packages as well? |
IMO I don't like monorepo because its version-to-version diffs are hard to understand. |
ping |
I’m not sure if that should be release as a major or minor version. Thoughts? |
Neither am I, but if I were the product owner I'd bump the major version because some users are required to change their application code. |
I would agree with a major bump since it could be a breaking change for consuming apps |
Okay in this case could you please rename the commit and include the breaking change message according to semantic versioning convention? |
Marked it as BREAKING CHANGE both in the PR title and the commit messages. Is it okay? |
I’ve adapted the commit message during the merge to comply semantic-versioning. Hopefully it’s going to be released as a major version. Thanks! |
Thanks! |
Not sure what's going on but travis CI can't trigger semantic release anymore. Can someone investigate? It says 403 but Im not sure what to do. |
@okonet I'll take a look when I have some free time. Hopefully today. |
🎉 This PR is included in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Any polyfills, not ponyfills which does not affect the global env, should be injected by the application, not by the library.
If you think this PR is okay, please add
"sideEffects": false
topackage.json
.This is a breaking change (i.e. semver-major) because it may require the application code changes.