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

Upgrade to node 20.12.2 #111

Closed

Conversation

Timodie
Copy link

@Timodie Timodie commented Aug 7, 2024

Description

Modeled after silvermine/videojs-airplay#54
This PR upgrades this project to node 20.12.2 but does not update the grunt-contrib-uglify version

Tim Addai added 5 commits August 7, 2024 18:55
Updates the .nvmrc to point node version 20.12.2
Creates the necessary scripts to support
commands that will be exeucted during the build
Uglify was configured to mangle/compress in
debug mode and beautify mode in
production.This should be reversed.
The CI steps need to be updated to use Node 20.
While doing so, we incorporated some additional work:
- Update all actions to use the latest versions that run on Node 20
- Update the test matrix to use our .nvmrc file as one of the Node
versions to test againsts
- Check for uncommitted changes after installing dependencies
@coveralls
Copy link

Coverage Status

coverage: 0.0%. remained the same
when pulling 6f505b3 on Timodie:taddai/upgrade-node-20.12.2
into a89750e on silvermine:master.

Copy link

@kmuncie kmuncie left a comment

Choose a reason for hiding this comment

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

Just a first pass review, @joshuacurtiss can take it from here

- run: npm run standards
- run: npm run build
Copy link

Choose a reason for hiding this comment

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

Is this missing the "Check for uncommitted changes" on purpose?

name: PUT NVM version in output
id: makeNodeVersionOutput
run: echo "nvmrc=$(cat .nvmrc)" >> "$GITHUB_OUTPUT"

Copy link

Choose a reason for hiding this comment

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

is this new line intended?

test:
needs: [ build ]
runs-on: ubuntu-latest
strategy:
fail-fast: false
matrix:
node-version: [ 14, 16, 'lts/*', 'latest' ]
node-version: [ 16,'${{ needs.build.outputs.nvmrc }}', 'lts/*', 'latest' ]
Copy link

Choose a reason for hiding this comment

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

Whitespace issue after the first comma

with:
node-version: ${{ matrix.node-version }}
- run: npm i -g [email protected]
- run: npm ci # Reinstall the dependencies to ensure they install with the current version of node
- run: npm test
Copy link

Choose a reason for hiding this comment

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

Should we be running the following before npm test?

         - run: npm run standards
         - run: npm run build # Ensure building is possible with this version of node

@@ -1 +1 @@
16.15.0
20.12.2
Copy link

Choose a reason for hiding this comment

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

I believe we are standardizing on including the v here

@@ -91,9 +91,9 @@ module.exports = function(grunt) {
banner: '/*! <%= pkg.name %> <%= grunt.template.today("yyyy-mm-dd") %> <%= versionInfo %> */\n',
sourceMap: true,
Copy link

Choose a reason for hiding this comment

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

I believe we also usually use DEBUG on this line and the following

@@ -4,8 +4,11 @@
"description": "video.js plugin for selecting a video quality or resolution",
"main": "src/js/index.js",
"scripts": {
"prepare": "grunt build",
"test": "check-node-version --npm 8.5.5 && nyc mocha -- 'tests/**/*.test.js'",
"prepare": "npm run build",
Copy link

Choose a reason for hiding this comment

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

The name prepare seems out of norm compared to our other projects. Should this be changed to prepublish?

"test": "check-node-version --npm 8.5.5 && nyc mocha -- 'tests/**/*.test.js'",
"prepare": "npm run build",
"check-node-version": "check-node-version --node $(cat .nvmrc) --npm 10.5.0 --print",
"test": "nyc mocha -- -R spec 'tests/**/*.test.js'",
Copy link

Choose a reason for hiding this comment

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

I don't see the -R "reporter" option configured in many other projects, is that intended to be added here where it wasnt present before?

@joshuacurtiss
Copy link
Contributor

Please reference #112.

@onebytegone
Copy link
Contributor

Superseded by #112

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.

5 participants