Skip to content

Conversation

@snitin315
Copy link
Member

This PR contains a:

  • bugfix
  • new feature
  • code refactor
  • test update
  • typo fix
  • metadata update

Motivation / Use-Case

Update ESLint v9

Breaking Changes

No

Additional Info

No

@codecov
Copy link

codecov bot commented Jul 11, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (21f4051) to head (a21d824).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master      #203   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            3         3           
  Lines           18        18           
  Branches         2         2           
=========================================
  Hits            18        18           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

eslint.config.js Outdated
import configWebpack from "eslint-config-webpack";

export default defineConfig([
globalIgnores(["node_modules", "dist", "coverage", "test/fixtures"]),
Copy link
Member

Choose a reason for hiding this comment

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

I think we don't need these ignores, they are default in our eslint configuration

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, right.

import { compile } from "coffeescript";

import schema from "./options.json";
import CoffeeScriptError from "./CoffeeScriptError";
Copy link
Member

Choose a reason for hiding this comment

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

Weird, ideally dirty should warn on this and ask about extension, dirty it is like preparing for ES modules, so no warnings for require, but yes for import, I will look today

Anyway good job, it is first dirty usage, so we will fix everything today and will start to migrate in other repos

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, makes sense.

Copy link
Member

Choose a reason for hiding this comment

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

Looks like import/extensions doesn't have ability to control such things, i.e. you can't enable/disable it for es modules or commonjs, the rules work for ES modules and CommonJS together, we need to report it to them, so let's postpone it, when we will migrate to ES modules we will change config and catch all cases

@alexander-akait alexander-akait merged commit 1d95240 into master Jul 11, 2025
17 checks passed
@alexander-akait alexander-akait deleted the eslint-9 branch July 11, 2025 12:49
@alexander-akait
Copy link
Member

@snitin315 Feel free to update other repos too

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.

3 participants