Skip to content

refactor(eslint)!: Prepare eslint for rollup 3 and upgrade eslint to newest version - #1309

Merged
lukastaegert merged 1 commit into
rollup:masterfrom
colingm:use-new-eslint
Oct 7, 2022
Merged

refactor(eslint)!: Prepare eslint for rollup 3 and upgrade eslint to newest version #1309
lukastaegert merged 1 commit into
rollup:masterfrom
colingm:use-new-eslint

Conversation

@colingm

@colingm colingm commented Oct 7, 2022

Copy link
Copy Markdown
Contributor

Rollup Plugin Name: plugin-eslint

This PR contains:

bugfix
feature
refactor
documentation

other

Are tests included?

yes (bugfixes and features will not be merged without tests)

no

Breaking Changes?

yes (breaking changes will not be merged unless absolutely necessary)

no

List any relevant issue numbers:

#1233
#1231
#1128
#1010

https://github.com/rollup/plugins/issues/796

Description

Prior to these changes, the eslint plugin was using an older
version of eslint that relied on a class called CLIEngine.
In newer versions this has now been deprecated and so upgrading
versions required also updating to using ESLint internally
instead. Ultimately this doesn't change the usage of the plugin
but some of the option names have changed for ESLint (notably
configFile needs to change to overrideConfigFile).

The main driving factor for this change is to prevent conflicts
that happen when using @rollup/plugin-typescript and this plugin
together. Without this update, eslint would run on the transpiled
code and so the error messages weren't as helpful. This update
will allow the two plugins to work well together and provide
helpful information about errors and warnings.

This work is also preparing eslint for the move to rollup 3 through
various package version updates.

BREAKING CHANGES:

options structure has changed due to moving from CLIEngine to ESlint. Review the new supported options below:
https://eslint.org/docs/latest/developer-guide/nodejs-api#-new-eslintoptions
requires Node 14

This work is also based on this abandoned pr: #663

*This is a duplicate PR after the other was closed due to the target branch being closed: #1236

@lukastaegert

Prior to these changes, the eslint plugin was using an older
version of eslint that relied on a class called CLIEngine.
In newer versions this has now been deprecated and so upgrading
versions required also updating to using ESLint internally
instead. Ultimately this doesn't change the usage of the plugin
but some of the option names have changed for ESLint (notably
configFile needs to change to overrideConfigFile).

The main driving factor for this change is to prevent conflicts
that happen when using @rollup/plugin-typescript and this plugin
together. Without this update, eslint would run on the transpiled
code and so the error messages weren't as helpful. This update
will allow the two plugins to work well together and provide
helpful information about errors and warnings.

This change also includes some necessary package updates to prepare
eslint for Rollup 3.

BREAKING CHANGES:
- options structure has changed due to moving from CLIEngine t
  ESlint. Review the new supported options below:
https://eslint.org/docs/latest/developer-guide/nodejs-api#-new-eslintoptions
- requires Node 14
@lukastaegert
lukastaegert merged commit eab819a into rollup:master Oct 7, 2022
@colingm
colingm deleted the use-new-eslint branch October 7, 2022 19:09
lukastaegert added a commit that referenced this pull request Oct 7, 2022
lukastaegert pushed a commit that referenced this pull request Oct 7, 2022
… version (#1309)

Prior to these changes, the eslint plugin was using an older
version of eslint that relied on a class called CLIEngine.
In newer versions this has now been deprecated and so upgrading
versions required also updating to using ESLint internally
instead. Ultimately this doesn't change the usage of the plugin
but some of the option names have changed for ESLint (notably
configFile needs to change to overrideConfigFile).

The main driving factor for this change is to prevent conflicts
that happen when using @rollup/plugin-typescript and this plugin
together. Without this update, eslint would run on the transpiled
code and so the error messages weren't as helpful. This update
will allow the two plugins to work well together and provide
helpful information about errors and warnings.

This change also includes some necessary package updates to prepare
eslint for Rollup 3.

BREAKING CHANGES:
- options structure has changed due to moving from CLIEngine t
  ESlint. Review the new supported options below:
https://eslint.org/docs/latest/developer-guide/nodejs-api#-new-eslintoptions
- requires Node 14
lukastaegert pushed a commit that referenced this pull request Oct 7, 2022
… version (#1309)

Prior to these changes, the eslint plugin was using an older
version of eslint that relied on a class called CLIEngine.
In newer versions this has now been deprecated and so upgrading
versions required also updating to using ESLint internally
instead. Ultimately this doesn't change the usage of the plugin
but some of the option names have changed for ESLint (notably
configFile needs to change to overrideConfigFile).

The main driving factor for this change is to prevent conflicts
that happen when using @rollup/plugin-typescript and this plugin
together. Without this update, eslint would run on the transpiled
code and so the error messages weren't as helpful. This update
will allow the two plugins to work well together and provide
helpful information about errors and warnings.

This change also includes some necessary package updates to prepare
eslint for Rollup 3.

BREAKING CHANGES:
- options structure has changed due to moving from CLIEngine t
  ESlint. Review the new supported options below:
https://eslint.org/docs/latest/developer-guide/nodejs-api#-new-eslintoptions
- requires Node 14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants