Skip to content

Conversation

@pharret31
Copy link
Contributor

No description provided.

@pharret31 pharret31 self-assigned this Sep 8, 2025
- run: /opt/bin/ec-linux-amd64 -v

- run: npm i eslint
- name: Install ESLint
Copy link

Choose a reason for hiding this comment

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

I see that eslint is listed in package.json so looks like npm ci should be able to restore necessary version without a manual search, nah?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Npm ci can only perform a clean install of everything that is listed in package-lock, but for the lint step we only need the eslint package, there's no reason to install all dependencies

Copy link

Choose a reason for hiding this comment

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

Oh, it's a little bit tricky approach, but formally everything alright here
We take specific version from the package-lock.json and we really need only eslint here for lint checks (for now)
So, everything legal :D

But in future, if eslint will require additional packages (such as plugins), it'll be more tricky to support it this way

@pharret31 pharret31 merged commit ef49cbc into DevExpress:master Sep 10, 2025
10 checks passed
@pharret31 pharret31 deleted the 1770-security-deps-lock-devextremeaspnetdata-github branch September 10, 2025 11:57
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