Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
N
next.js
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Alex
next.js
Commits
dfe7c465
Commit
dfe7c465
authored
Oct 25, 2018
by
Michael Herold
Committed by
Tim Neutkens
Oct 25, 2018
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Updated contributing steps for next-server (#5405) (#5518)
parent
def2ce7e
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
11 additions
and
7 deletions
+11
-7
contributing.md
contributing.md
+11
-7
No files found.
contributing.md
View file @
dfe7c465
...
@@ -7,7 +7,7 @@ Our Commitment to Open Source can be found [here](https://zeit.co/blog/oss)
...
@@ -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:
...
@@ -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
```
```
Then
`next`
needs to link to
`next-server`
, and be linked itself:
```
```
cd packages/next
npm link
npm link
npm link next-server
```
```
And finally, link the
`next`
package inside your app:
Then link the
`next`
package inside your app:
```
```
npm link next
npm link next
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment