Skip to content

Conversation

@vas3a
Copy link
Collaborator

@vas3a vas3a commented Dec 16, 2025

re-build package lock for tc-core-library-js

@vas3a vas3a merged commit 196f8f1 into develop Dec 16, 2025
5 of 6 checks passed
@vas3a vas3a deleted the fix-package-lock branch December 16, 2025 16:34
- run:
name: App npm install
command: npm install
command: npm ci

Choose a reason for hiding this comment

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

[⚠️ correctness]
Switching from npm install to npm ci is a good choice for CI environments as it ensures a clean and consistent installation of dependencies based on the package-lock.json. However, ensure that the package-lock.json is up-to-date and correctly reflects the desired state of dependencies, as npm ci will fail if there are any discrepancies.

RUN npm config set unsafe-perm true
RUN git config --global url."https://git@".insteadOf git://
RUN npm install
RUN npm ci

Choose a reason for hiding this comment

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

[⚠️ correctness]
Switching from npm install to npm ci is a good practice for CI/CD environments as it ensures a clean install based on the package-lock.json. However, ensure that the package-lock.json is up-to-date and committed to the repository to avoid potential discrepancies between local and CI environments.

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