-
Notifications
You must be signed in to change notification settings - Fork 13
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
Fix up failing checks #127
Conversation
agjohnson
commented
Sep 13, 2023
- Build assets missed
- Drop unused tests
- Update package lock
- Don't install NPM 10 at RTD
- Build assets missed - Drop unused tests - Update package lock - Don't install NPM 10 at RTD
I gave a quick try to fixing the tests temporarily, but I think web-test-runner is bound to give us less problems here, and supports ES6 modules natively where Jest needs more hand holding. I'd say let's aim for #73 to resolve the tests |
@@ -11,7 +11,7 @@ build: | |||
- sphinx-build -b html docs/ $READTHEDOCS_OUTPUT/html | |||
|
|||
# Bundle the current version | |||
- npm install -g npm@latest | |||
- npm install -g npm@next-9 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is "next-9" here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an NPM dist tag that can be used (latest
is also a dist tag). For instance, you can see the tags for the npm
package with:
npm show npm
next-9
should point to the latest in the 9 series.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, OK. BTW, I'm using nodejs 18.15.0 and npm 9.5.0 locally.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aye, same. NPM 10 started requiring Node 18.17+ or something, but also I don't know we need bleeding edge NPM either way.