-
Notifications
You must be signed in to change notification settings - Fork 62
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(cleanup): Add prettier and remove babel #178
Conversation
url: `https://api.github.com/repos/${repo}/releases/latest` | ||
}) | ||
ctx.latestReleaseInfo = response.data | ||
} catch (err) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤦♂
}) | ||
ctx.latestReleaseTarballStream = response.data | ||
} catch (err) { | ||
throw err |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love it 😬
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👏 Amazing job! one small comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the cleanup, @jroehl. Have one question which I've written below and a suggestion to use chore
instead of feat
when squashing commits and merging the PR.
If we use chore we won't have a new release with the changes. However, one can argue that this is not a suer facing release and it can wait to another proper release |
Yeah, that's my point @Khaledgarbaya. Not to have a release based on changes that aren't user-facing and it's really a chore. |
🎉 This PR is included in version 1.1.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Summary
Remove transpilation and introduce prettier.
Description
Motivation and Context
To simplify keeping dependencies up to date and remove unnecessary complexity from the build/lint/develop process, we can remove babel, a custom eslint config from the codebase. Instead we can rely on an opinionated linter (
prettier
) and use the built-in features of node >= 8, getting rid of the transpilation process.Todos
Screenshots (if appropriate):