[#422] Change to use @nimblehq/eslint-config-nimble-core
#507
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@nimblehq/eslint-config-nimble-core
#422What happened 👀
As we have separated the previous version of
eslint-config-nimble
into many child packages with the main one beingeslint-config-nimble-core
, and we don't needeslint
rules forreact
, ortypescript
.Therefore, we change to use the
@nimblehq/eslint-config-nimble-core
package.Insight 📝
Warning
Published a new version for the
core
package, but I forgot to remove theparser
which hasn't been defined in the correspondingpackage.json
-> Needs one more update before using it.After updating the version of the core package, there was a warning about the outdated usage of
.eslintignore
, then we switched to using theconfig file
instead.Proof Of Work 📹