Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

split test steps without duplicate build, fix lock file #337

Merged
merged 1 commit into from
Oct 15, 2023

Conversation

Aprillion
Copy link
Collaborator

No description provided.

@Aprillion Aprillion mentioned this pull request Oct 7, 2023
7 tasks
@Aprillion
Copy link
Collaborator Author

FYI @jrhender

@@ -15,7 +15,8 @@ jobs:
run: |
npm ci
npm run lint
npm run build
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is this because the test script is currently npm run build && jest, so npm run build is being run twice? I think this is ok as an optimization, however my concern would be that if the test script changes, then the CI is no longer running a build.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

well, if the test fails because of not running a build, we will notice 😅

@@ -49,7 +49,7 @@
"wrangler": "^2.10.0"
},
"engines": {
"node": ">=16"
"node": ">=18"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Ah thanks, perhaps I forgot to run npm install to update package-lock after increasing the engine version in package.json 🤔 ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

yup, fortunately no other changes were missing

@Aprillion Aprillion merged commit 8586087 into master Oct 15, 2023
1 check passed
@Aprillion Aprillion deleted the update-test branch October 15, 2023 07:38
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