-
-
Notifications
You must be signed in to change notification settings - Fork 274
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: tapjs/tapjs
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: tap@18.6.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: tapjs/tapjs
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: tap@18.7.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 16 commits
- 133 files changed
- 2 contributors
Commits on Dec 9, 2023
-
Configuration menu - View commit details
-
Copy full SHA for 7b79b31 - Browse repository at this point
Copy the full SHA 7b79b31View commit details
Commits on Jan 18, 2024
-
tapjs/mock: work around ESM hook deadlock
When an ESM hook depends on the main thread to respond, and is registered prior to another ESM hook being registered, it can deadlock because the loader freezes the main thread to execute the registration pseudo-synchronously. In other words: - mock loader is registered, now all resolve/load actions will await a response from the main thread - next loader tries to register, using the mock loader (and all previous loaders, in fact), *pausing the main thread* to resolve the loader module. - because main thread is paused, @tapjs/mock hook never completes, because main thread cannot respond. The solution here is not really very elegant for solving this problem, but is a worthwhile optimization in its own right. The client will do nothing and just fall back to default load/resolve until it gets a message from the service on the main thread saying that it's been activated. This message is sent the first time the user calls `t.mockImport`, since before then there's definitely nothing to mock anyway.
Configuration menu - View commit details
-
Copy full SHA for 410f1ac - Browse repository at this point
Copy the full SHA 410f1acView commit details -
Configuration menu - View commit details
-
Copy full SHA for eb060c7 - Browse repository at this point
Copy the full SHA eb060c7View commit details
Commits on Jan 19, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 5e28526 - Browse repository at this point
Copy the full SHA 5e28526View commit details -
Configuration menu - View commit details
-
Copy full SHA for 81dd0ad - Browse repository at this point
Copy the full SHA 81dd0adView commit details -
Would've found that build failure issue.
Configuration menu - View commit details
-
Copy full SHA for 4b33e42 - Browse repository at this point
Copy the full SHA 4b33e42View commit details -
Configuration menu - View commit details
-
Copy full SHA for 51e8a31 - Browse repository at this point
Copy the full SHA 51e8a31View commit details -
chore: use --loader in bootstrap
The CI was failing for older node versions, because the bootstrap script was updated to use `--import` instead of `--loader`, which of course is not going to work for old node versions. Could have a switch, but since `--loader` still works, may as well just leave it using the older style, as long as node < 20 is still supported.
Configuration menu - View commit details
-
Copy full SHA for 5063b46 - Browse repository at this point
Copy the full SHA 5063b46View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0768324 - Browse repository at this point
Copy the full SHA 0768324View commit details -
Configuration menu - View commit details
-
Copy full SHA for dc8dadd - Browse repository at this point
Copy the full SHA dc8daddView commit details
Commits on Jan 25, 2024
-
Configuration menu - View commit details
-
Copy full SHA for e906d21 - Browse repository at this point
Copy the full SHA e906d21View commit details -
Configuration menu - View commit details
-
Copy full SHA for ae2deb7 - Browse repository at this point
Copy the full SHA ae2deb7View commit details -
1
Configuration menu - View commit details
-
Copy full SHA for f105701 - Browse repository at this point
Copy the full SHA f105701View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2f9abd3 - Browse repository at this point
Copy the full SHA 2f9abd3View commit details -
remove shell:true from publish script
I don't publish from Windows anyway.
Configuration menu - View commit details
-
Copy full SHA for 5bb7ca8 - Browse repository at this point
Copy the full SHA 5bb7ca8View commit details -
@tapjs/worker@1.1.18 @tapjs/typescript@1.4.0 @tapjs/tsx@1.1.19 @tapjs/test@1.4.0 tap@18.7.0 @tapjs/synonyms@1.1.18 @tapjs/stdin@1.1.18 @tapjs/spawn@1.1.18 @tapjs/snapshot@1.2.18 @tapjs/sinon@1.1.18 @tapjs/run@1.5.0 @tapjs/reporter@1.3.16 @tapjs/node-serialize@1.3.0 @tapjs/nock@3.1.18 @tapjs/mock@1.3.0 @tapjs/mocha-globals@1.1.18 @tapjs/intercept@1.2.18 @tapjs/fixture@1.2.18 @tapjs/filter@1.2.18 @tapjs/esbuild-kit@1.1.19 @tapjs/dummy-plugin@1.1.20 @tapjs/create-plugin@1.1.18 @tapjs/core@1.5.0 @tapjs/config@2.4.15 @tapjs/clock@1.1.18 @tapjs/before-each@1.1.18 @tapjs/before@1.1.18 @tapjs/asserts@1.1.18 @tapjs/after-each@1.1.18 @tapjs/after@1.1.18
Configuration menu - View commit details
-
Copy full SHA for 5187113 - Browse repository at this point
Copy the full SHA 5187113View commit details
There are no files selected for viewing