10574b7359
* wip * webpack loader working * time to switch to babel * wip * wip - next broken * build & babel working, but resolver not loaded at runtime * webpack loaders fully working! * rpc server handler ported * fully working e2e! * ci * fix * fix * fix test * refactor integration test setup * port rpc integration test * remove duplicate constants * fix timeout * add more explicit timeouts for tests * use pnpm exec * add custom _document for auth test * await killapp * add next as dependency for test utils * update pnpm ci * add vitest config file * add hookTimeout to global vitest file Co-authored-by: Dillon Raphael <dillon@creatorsneverdie.com>
1.2 KiB
1.2 KiB
Contributing
Read the Contributing Guide at Blitzjs.com
To run tests
Make sure you have chromedriver installed for your Chrome version. You can install it with
brew install --cask chromedriveron Mac OS Xchocolatey install chromedriveron Windows- Or manually download the version that matches your installed chrome version (if there's no match, download a version under it, but not above) from the chromedriver repo and add the binary to
<next-repo>/node_modules/.bin
You may also have to install Rust and build our native packages to see all tests pass locally. We check in binaries for the most common targets and those required for CI so that most people don't have to, but if you do not see a binary for your target in packages/next/native, you can build it by running yarn --cwd packages/next build-native. If you are working on the Rust code and you need to build the binaries for ci, you can manually trigger the workflow to build and commit with the "Run workflow" button.
Running all tests:
pnpm test