Closed Chriscbr closed 2 weeks ago
Thanks for opening this pull request! :tada: Please consult the contributing guidelines for details on how to contribute to this project. If you need any assistance, don't hesitate to ping the relevant owner over Discord.
Topic | Owner |
---|---|
Wing SDK and utility APIs | @chriscbr |
Wing Console | @ainvoner , @skyrpex , @polamoros |
JSON, structs, primitives and collections | @hasanaburayyan |
Platforms and plugins | @hasanaburayyan |
Frontend resources (website, react, etc) | @tsuf239 |
Language design | @chriscbr |
VSCode extension and language server | @markmcculloh |
Compiler architecture, inflights, lifting | @yoav-steinberg |
Wing Testing Framework | @tsuf239 |
Wing CLI | @markmcculloh |
Build system, dev environment, releases | @markmcculloh |
Library Ecosystem | @chriscbr |
Documentation | @hasanaburayyan |
SDK test suite | @tsuf239 |
Examples | @hasanaburayyan |
Wing Playground | @eladcon |
Console preview environment is available at https://wing-console-pr-6676.fly.dev :rocket:
Thanks for contributing, @Chriscbr! This PR will now be added to the merge queue, or immediately merged if rybickic/update-vitest
is up-to-date with main
and the queue is empty.
Congrats! :rocket: This was released in Wing 0.74.51.
Closes #6675
I thought for a hot minute that vitest deprecated thread-based workers and so this change would have required a lot more refactoring, thankfully they still support fork-based workers, it's just under a different option now. (Many tests within the Wing CLI package depend on
process.chdir()
).Checklist
pr/e2e-full
label if this feature requires end-to-end testingBy submitting this pull request, I confirm that my contribution is made under the terms of the Wing Cloud Contribution License.