-
Notifications
You must be signed in to change notification settings - Fork 41
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
Update package.json #102
Update package.json #102
Conversation
Add `"sideEffects": false` for better codspliting
@ckifer I need you help. We need to go a quick 2 minute adventure. |
Not sure what you mean about a 2 minute adventure. I'm fine with doing this, but it may not help as much as it seems it might |
When can we wait for new publich patch version? |
Are you saying publish in general or publish and then install in recharts? I can publish it as soon as a get a few minutes. I can't install it in recharts 2.x, only once 3.0 is out because it goes across a breaking change (3.0 to 4.0) |
can we patch 3 and 4 versions? |
generally I wouldn't go back and patch 3.x no. Being that this is a small change it shouldn't be a huge deal |
Ok, will think about 4 mirgation |
are using using |
|
you need any help? |
these were the documented breaking changes https://github.com/recharts/react-smooth/releases/tag/v4.0.0 No migration required if none of those things effect you. I shouldn't need help, just need a minute to take care of the release |
@denisx released in 4.0.2 |
and actually scratch that about the 3.0 to 4.0 thing recharts uses 4.0 in the master (2.x) branch so all good |
Let me know how much this actually helps your code splitting |
will i need to make a pr to rechart? because *.lock file does not up the version of deps itself (or it does any other package) |
The caret (^) takes care of that. If you update your dependencies it should automatically install the latest patch version of react-smooth |
if both packages at one project... |
react-smooth is installed implicitly because it is a dependency of recharts. Just run npm update and check your lock file to make sure it updated |
i think this is a bit mistake at package.json / files. no |
good catch. I started migrating to TS and looks like the build process isn't quite right |
4.03 published |
@denisx let me know as soon as you can try it :/ apologies for the miss there |
Add
"sideEffects": false
for better codspliting