Please consider the following

[Hypercubed]

A few suggestions I think we can consider:

• Get the current project name from the name attribute in the package.json instead of the folder name.
• Migrate from eslint with custom rules to xo.
• Use eslint-plugin-node to ensure post node v4 features are not accidentally added.

[lannonbr]

I could try working on these. I'll work on the two linter tasks first and then the task to get the current project name afterwards.

[Hypercubed]

Hi @lannonbr , if you can start with # 3 (the eslint-node-plugin). We should get a 👍 from @stefanjudis before # 2.

[lannonbr]

Okay, so you want any of the eslint-plugin-node rules changed or just have them use the defaults?

[lannonbr]

I implemented the first task in PR #99.

[Hypercubed]

@lannonbr Just the defaults for eslint-plugin-node , Be sure to add the engines object to the package. See here: stefanjudis/credits@38b1c7f

[lannonbr]

@Hypercubed Okay, I can work on that in about 4 hours. I'll notify you if I have any issues.

[stefanjudis]

Well yeah. 2. and 3. are fine for me...

What's the benefit of 2? I don't mind, just out of curiosity. :)

[Hypercubed]

@stefanjudis Re # 2 , mostly personal preference, but for FWIW:

1. I find the current eslint rules awkward. For a project with multiple contributors may be better to select a common set.
2. It seems some reasonable eslint rules are not enabled, for example, checks for unused variables.
3. I really like the xo atom plugin.
4. xo, as opposed to standard or semi-standard, allows overriding the default rules.

[stefanjudis]

I find the current eslint rules awkward. For a project with multiple contributors may be better to select a common set

Well yeah. Personal preference. ¯_(ツ)_/¯
When you mean the spacing, if it bothers you so much, go ahead. 😄

[Hypercubed]

Doesn't bother me that much. At least you have semicolons.

Edit: and I need spell-check.

[stefanjudis]

At least you have semicolens.

Haha, yes! 🎉