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

Chore: Increase node version minimums to 10.13 #13725

Merged
merged 1 commit into from
Jan 28, 2021

Conversation

phated
Copy link
Contributor

@phated phated commented Jan 25, 2021

Issue: #8207

What I did

In #8207, the storybook CI was changed to only be node 10+ but the engine fields weren't changed to reflect that supported version range. I've updated all the engine references to be >=10.13 (which is when recursive mkdir was added) to be inline with the CI test matrix.

Additionally, node 8 is no longer LTS after Jan 1, 2021.

I also updated the babel settings to target node 10 (plucked from #11220).

How to test

  • Is this testable with Jest or Chromatic screenshots? ❌
  • Does this need a new example in the kitchen sink apps? ❌
  • Does this need an update to the documentation? ❌

If your answer is yes to any of these, please make sure to include it in your PR.

@phated phated added the maintenance User-facing maintenance tasks label Jan 25, 2021
@phated phated requested review from shilman and ndelangen January 25, 2021 20:27
@shilman shilman changed the title chore: increase node version minimums to 10.13 Chore: Increase node version minimums to 10.13 Jan 28, 2021
Copy link
Member

@shilman shilman left a comment

Choose a reason for hiding this comment

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

LGTM 🎉

@shilman shilman merged commit 05facd2 into storybookjs:next Jan 28, 2021
@phated phated deleted the phated/node-versions branch January 28, 2021 18:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance User-facing maintenance tasks
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants