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.

Sign up for GitHub

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

Jump to bottom

Test using multiple runtimes #27

Open
jorins opened this issue Dec 15, 2023 · 1 comment
Open

Test using multiple runtimes #27

jorins opened this issue Dec 15, 2023 · 1 comment
Labels
infrastructure Relating to the project's structure and CI/CD wontfix This will not be worked on

Comments

@jorins
Copy link
Contributor

jorins commented Dec 15, 2023

We could and should run our tests against multiple runtimes. This includes node versions as well as deno and bun. Deno appears to have support for both node:test and node:assert and the tests should run as is. Bun reports support for node:assert but not node:test and probably won't work.

I considered testing against multiple TypeScript versions, but TS doesn't do semver or any notion of LTS.
@jorins
Copy link
Contributor Author

jorins commented Dec 15, 2023

After testing a bit with Deno and seeing converting from describe to test turn into yak-shaving, I don't think it's worth pursuing other runtimes presently. Creating a separate issue for matrix testing node versions though.

@jorins jorins added enhancement New feature or request wontfix This will not be worked on infrastructure Relating to the project's structure and CI/CD and removed enhancement New feature or request labels Dec 15, 2023
@jorins jorins mentioned this issue Dec 16, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
infrastructure Relating to the project's structure and CI/CD wontfix This will not be worked on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jorins