-
Notifications
You must be signed in to change notification settings - Fork 0
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
Re-enable edge environment testing #6
Comments
Merged
tnez
added a commit
that referenced
this issue
Jun 30, 2023
Re-enable edge-environment for unit tests in CI (closes #6)
Merged
tnez
pushed a commit
that referenced
this issue
Jun 30, 2023
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @tnezdev/actions@0.3.1 ### Patch Changes - b17bfb8: Add license (`Apache 2.0`) - f48413d: Re-enable edge-environment for unit tests in CI (closes #6) - 9a7833e: fix: add missing type exports (closes #24) The documentation gives an example of doing something like this: ```ts import { createAction } from "@tnezdev/actions"; import type { ActionHandler } from "@tnezdev/actions"; type Conetxt = {}; type Input = {}; type Output = {}; const handler: ActionHandler<Context, Input, Output> = () => {}; ``` However, the `ActionHandler` type was not being exported before this fix. Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I had to temporarily disable the edge environment testing because it did not play nicely with the auto mocking behavior in Jest. It seems the auto-mocking does some kind of
eval
from string which is disabled inedge-runtime
.Need to:
package.json
to:"test": "jest --env @edge-runtime/jest-environment .test.ts && jest --env node .test.ts",
action.test.ts
so that they work in the@edge-runtime/jest-environment
The text was updated successfully, but these errors were encountered: