-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Testing Improvements #176
Comments
I don't know if this is visible without a GitKraken account, but here's a patch for offline testing for now: https://gitkraken.dev/link/drafts/ba02a3a7-4beb-4ed9-aac8-447540488f70?type=patch |
Yay! One of my issues was "yet another longstanding NPM bug™," so it can be removed from this list, at least. |
It is not, unfortunately. |
I figured. Why do they have to overwrite copy-as-patch? Well, there's the actual patch: diff --git a/test/run.sh b/test/run.sh
index 86bccb7..1c38065 100755
--- a/test/run.sh
+++ b/test/run.sh
@@ -163,9 +163,9 @@ else
echo -e '\x1B[33m-- Testing runs\x1B[0m'
fi
-PACKAGE_PATH=$(npm pack -s ../ | tail -n 1)
+PACKAGE_PATH=$(npm pack --offline -s ../ | tail -n 1)
echo "Package path is $PACKAGE_PATH"
-npm install -g $PACKAGE_PATH
+npm install --offline -g $PACKAGE_PATH
# init
diff --git a/turbo.json b/turbo.json
index 92ac8f8..82d6d2c 100644
--- a/turbo.json
+++ b/turbo.json
@@ -18,8 +18,7 @@
"tsc",
"eslint-check",
"prettier-check",
- "jest",
- "test-run"
+ "jest"
]
},
"eslint-check": { And the message:
|
FYI, tests are all failing in CI right now. Not sure why. |
Finally got a chance to check this out, new elm-syntax broke tests again. EDIT: Fixed on #197 |
And again, in 7.3.5 😢 |
I wrote a quick branch swapping to vitest last night, and it's fast. Disclaimer: only supports node 18+, so not really an option right now. |
octokit
?1 (we get types to replace tests)diff
(Improve shell scripts #193)Footnotes
Alternatively,
ungh
would help with rate limiting and types onceofetch
finishes adding in support for statically typing API endpoints (https://github.com/unjs/ungh/issues/4#issuecomment-1401762324). ↩The text was updated successfully, but these errors were encountered: