terribleplan/next.js
1
0
Fork 0
mirror of https://github.com/terribleplan/next.js.git synced 2024-01-19 02:48:18 +00:00
Code Issues Releases Wiki Activity

Updated contributing steps for next-server (#5405) (#5518)

Browse source
This commit is contained in:
Michael Herold 2018-10-25 13:51:20 -07:00 committed by Tim Neutkens
parent def2ce7eda
commit dfe7c4652f
1 changed files with 13 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
contributing.md
View file

@ -7,7 +7,7 @@ Our Commitment to Open Source can be found [here](https://zeit.co/blog/oss)
3. Run `npm run bootstrap`, which will link all repositories locally 3. Run `npm run bootstrap`, which will link all repositories locally
4. Run `npm run dev` to build and watch for code changes 4. Run `npm run dev` to build and watch for code changes
### To run tests ## To run tests
Running all tests: Running all tests:
@ -27,26 +27,30 @@ Running just one test in the `production` test suite:
yarn testonly --testPathPattern "production" -t "should allow etag header support" yarn testonly --testPathPattern "production" -t "should allow etag header support"
``` ```
### Running the integration test apps without running tests ## Running the integration test apps without running tests
``` ```
./node_modules/.bin/next ./test/integration/basic ./node_modules/.bin/next ./test/integration/basic
``` ```
### Testing in your own app ## Testing in your own app
You only have to link the package once: First `next-server` needs to be linked:
```
cd packages/next
```
``` ```
cd packages/next-server
npm link npm link
``` ```
Then `next` needs to link to `next-server`, and be linked itself:
Then link the `next` package inside your app: ```
cd packages/next
npm link
npm link next-server
```
And finally, link the `next` package inside your app:
``` ```
npm link next npm link next