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

update tooling (rollup, etc) (ignore red x, it is coveralls) #1931

Merged
merged 7 commits into from
Jun 4, 2019

Conversation

xaviergonz
Copy link
Contributor

@xaviergonz xaviergonz commented Mar 17, 2019

This kind of big PR is all about tooling:

  • updated all dev deps to latest versions (except for flow and chalk)
  • fixed configurations to work with the changes
  • changed the build script so it only uses rollup + plugins (no more envify, browserify, uglify, etc)
  • since rollup uglify uses terser rather than the buggy uglify-es the code is less likely to have weird minification bugs
  • changed some eslint settings that were conflicting with TS itself
  • fixed eslint errors on tests (mostly about the usage of var and unused variables)
  • fixed ts tests not actually using the proper tsconfig

no actual source code was changed other than tests (AFAI remember) :)

note that the decrease in coverage is most probably the update of jest doing a better job at detecting uncovered lines

@xaviergonz xaviergonz changed the title update tooling update tooling (please ignore coveralls red x) Mar 17, 2019
@coveralls
Copy link

coveralls commented Mar 17, 2019

Coverage Status

Coverage decreased (-0.7%) to 93.219% when pulling a9d4c6e on update-tooling into d15b5c0 on master.

@xaviergonz xaviergonz changed the title update tooling (please ignore coveralls red x) update tooling Mar 17, 2019
@xaviergonz xaviergonz changed the title update tooling update tooling (rollup, etc) Mar 17, 2019
@xaviergonz xaviergonz changed the title update tooling (rollup, etc) update tooling (rollup, etc) (ignore red x, it is coveralls) Mar 30, 2019
@mweststrate
Copy link
Member

@xaviergonz in the category of "if it ain't broken, don't fix it", any special highlights that make it important to merge this? In general I don't have any trouble swapping tools around, but in MobX's case it is a little bit more trickier, since every change on master is cherry-picked to the mobx4 branch, it is really valuable to not touch or divert too many things (or, obviously, do it on both). That is for example the reason why the tests are all still in es5 / var style.

@mweststrate
Copy link
Member

I think I'm just asking, how hard is it to do the same on the mobx4-master branch 🙈

@xaviergonz
Copy link
Contributor Author

windows compatibility mostly :) It is a bit annoying to be forced to switch to WSL just to work on mobx.

Also using terser for minification I'd say is a big plus, since uglifyJs has had bugs that haven't been fixed in like... forever, and those have bitten me more than once in production versions, while I still haven't had a single issue with terser.

How hard? dunno, I could try to cherry pick it into the mobx4 branch and see what happens?

@mweststrate
Copy link
Member

mweststrate commented Apr 17, 2019 via email

@xaviergonz xaviergonz mentioned this pull request Apr 20, 2019
@xaviergonz
Copy link
Contributor Author

Similar pr open for mobx 4

@mweststrate
Copy link
Member

Merged! Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants