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

Cleanup node_modules, update packages #1894

Merged
merged 2 commits into from
Mar 7, 2019
Merged

Conversation

kitsonk
Copy link
Contributor

@kitsonk kitsonk commented Mar 7, 2019

This PR updates the package.json to do a bit of cleanup as well as "pin" all the versions that are installed so there is a lower risk of them "floating" to unintended versions.

Also, this PR introduced a .yarnclean which removes non-essential files when yarn is run to install or update packages. This will help keep

Also, this moves from ts-simple-ast to the renamed project ts-morph.

There were a few regressions in the library builder (independent of ts-simple-ast that occurred when doing a clean install of the node_modules which needed to be addressed, but also improved the logging of the tool which helped in isolating the issues.

@kitsonk
Copy link
Contributor Author

kitsonk commented Mar 7, 2019

Hmmm the lint failures are not related to this PR, there came in another commit, but it seems for whatever reason, linting wasn't effectively running for a while until this PR got it working again. I will make the changes.

Copy link
Member

@ry ry left a comment

Choose a reason for hiding this comment

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

LGTM no comments - thanks for this!

Regarding lint - I checked that it is currently working - it is. So the changes must be do to the upgrade.

@ry ry merged commit 0473d83 into denoland:master Mar 7, 2019
@kitsonk
Copy link
Contributor Author

kitsonk commented Mar 7, 2019

Interesting side effect, we used to lose the typescript.js.map in the bundling processes (which made some of the stack traces not make sense when a compiler error occurs) but now with the upgrade rollup, it has increased the size of the binary.

@ry
Copy link
Member

ry commented Mar 8, 2019

@kitsonk Ok - the increase is negligible - thanks. 77mb -> 81mb.
In the future if we want to prune binary size I will know to get rid of that one : )

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.

None yet

2 participants