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

Move babel and eslint configuration to package.json #405

Merged
merged 1 commit into from
Apr 5, 2017

Conversation

coryhouse
Copy link
Owner

It's easy to overlook .babelrc and .eslintrc when copying files, especially on Windows. So I think it makes sense to move them to package.json. Many other boilerplates use this approach as well.

What does everyone think?

@coryhouse coryhouse requested review from nickytonline and kwelch April 4, 2017 13:06
@coryhouse coryhouse changed the title Move babel and eslint to package.json Move babel and eslint configuration to package.json Apr 4, 2017
@coveralls
Copy link

coveralls commented Apr 4, 2017

Coverage Status

Coverage remained the same at 95.283% when pulling 2e1b094 on move-babel-and-eslint-to-package-json into 0274261 on master.

@@ -1,6 +1,6 @@
{
"name": "react-slingshot",
"version": "5.0.0",
"version": "7.0.0",
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why the big version hike?

Copy link
Owner Author

Choose a reason for hiding this comment

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

Well embarrassingly, when I announced 6.0, I didn't update package.json to reflect it. I would consider the config move a breaking change, so that's why I went to 7. Make sense?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Yeah, I forgot the current release was 6.0, so I was mostly trying to figure how one change was 2 version. All good by me.

Copy link
Collaborator

Choose a reason for hiding this comment

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

same here.

Copy link
Collaborator

@kwelch kwelch left a comment

Choose a reason for hiding this comment

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

I am good with this. I know this came up a while back on twitter. My only concern is size of the package.json is have many purposes now.

May be a good next step to add a script that moves it from package.json to rc files. This actually may be good as a stand alone packaged-cli tool.

@nickytonline
Copy link
Collaborator

I'm fine with the change as well. Might as well stop causing headaches for Windows users.

@coryhouse
Copy link
Owner Author

The size of package.json wouldn't be bad if we dropped all the custom eslint rules. I'd like to consider dumping all custom rules and just use eslint's recommended as a basline. Thoughts on that?

@nickytonline
Copy link
Collaborator

nickytonline commented Apr 4, 2017 via email

@kwelch
Copy link
Collaborator

kwelch commented Apr 4, 2017

I agree for the purposes of this repo a baseline/standard rule list may be better suited.

Any updates we can make to the babel config to make that cleaner? Maybe introduce babel-preset-env.

@nickytonline
Copy link
Collaborator

@coryhouse, I'll take a peek tonight at your PR.

Copy link
Collaborator

@nickytonline nickytonline left a comment

Choose a reason for hiding this comment

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

@coryhouse, I grabbed your PR locally and ran it. We're all good to go.

@@ -1,6 +1,6 @@
{
"name": "react-slingshot",
"version": "5.0.0",
"version": "7.0.0",
Copy link
Collaborator

Choose a reason for hiding this comment

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

same here.

@nickytonline
Copy link
Collaborator

@kwelch anything else to add before I merge?

@kwelch
Copy link
Collaborator

kwelch commented Apr 5, 2017

I am good, I think there are few action items from this around the lint and babel configs. Should we open an issue for those to discuss?

@nickytonline
Copy link
Collaborator

@kwelch, yeah, can you open another issue for that?

@kwelch kwelch mentioned this pull request Apr 5, 2017
@nickytonline nickytonline merged commit aa34f0d into master Apr 5, 2017
@kwelch kwelch mentioned this pull request Feb 12, 2018
@nickytonline nickytonline deleted the move-babel-and-eslint-to-package-json branch April 28, 2019 05:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants