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

Use asterisk for @types/* dependencies #3131

Merged
merged 2 commits into from Sep 26, 2019
Merged

Conversation

frenzzy
Copy link
Contributor

@frenzzy frenzzy commented Sep 25, 2019

This PR contains:

  • bugfix
  • feature
  • refactor
  • documentation
  • other

Are tests included?

  • yes (bugfixes and features will not be merged without tests)
  • no

Breaking Changes?

  • yes (breaking changes will not be merged unless absolutely necessary)
  • no
  • not sure

List any relevant issue numbers:

Description

Could we use asterisk instead of fixed version for @types/node and possible other @types/* dependencies?

This is how DefinitelyTyped publish their packages with dependencies to other typings (for example see @types/react/package.json). It allows users to instal a single version of package with necessary typings.

I believe that it may reduce the size of node_modules folder.

frenzzy and others added 2 commits September 25, 2019 23:38
Could we use asterisk instead of fixed version for `@types/node` and possible other `@types/*` dependencies?

This is how [DefinitelyTyped](https://github.com/DefinitelyTyped/DefinitelyTyped) publish their packages with dependencies to other typings (for example see [`@types/react/package.json`](https://unpkg.com/browse/@types/react/package.json)). It allows users to instal a single version of package with necessary typings.

I believe that it may reduce the size of `node_modules` folder.
Copy link
Member

@lukastaegert lukastaegert left a comment

Choose a reason for hiding this comment

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

Thanks, makes sense. Hope I do not break it when updating dependencies in the future 🙄. Will still try to keep the lockfile on the latest versions, though.

@codecov
Copy link

codecov bot commented Sep 26, 2019

Codecov Report

Merging #3131 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #3131   +/-   ##
=======================================
  Coverage   89.32%   89.32%           
=======================================
  Files         165      165           
  Lines        5732     5732           
  Branches     1741     1741           
=======================================
  Hits         5120     5120           
  Misses        379      379           
  Partials      233      233

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4b69c09...4ce0f31. Read the comment docs.

@lukastaegert lukastaegert merged commit bc5b98d into rollup:master Sep 26, 2019
@frenzzy frenzzy deleted the patch-1 branch September 26, 2019 15:25
@Feiyang1
Copy link

Feiyang1 commented Oct 4, 2019

@lukastaegert seems 1.23.0 regressed on it and has "@types/node": "^12.7.10"

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

3 participants