You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.project.md
+26-2Lines changed: 26 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,10 +58,10 @@ Note that these `ddev` commands _must_ be run in the `services/app` directory.
58
58
59
59
## Helpful commands
60
60
61
-
#### Monitoring the applications
61
+
### Monitoring the applications
62
62
If you want to monitor the status of `app` or `storybook`. Please use `ddev nextjs monit`
63
63
64
-
#### Restarting a specific service
64
+
### Restarting a specific service
65
65
If you want to restart `storybook` or `app`, please use the following:
66
66
67
67
`app`
@@ -151,3 +151,27 @@ with the option to include a Storybook story file as well.
151
151
* Starting in Next.js v9.4, TypeScript errors do not show up in your browser when running the dev server (i.e. `npm run dev`). However, TS errors will prevent `next build` (i.e. `npm run build`) from running successfully. Be sure to run `npm run lint` and `npm run tsc` before committing and pushing code. This will give you lint and TS errors that will most likely cause your builds to fail.
152
152
* For discussion: should we include a [TS checker in the config](https://github.com/vercel/next.js/issues/12735#issuecomment-629404102)? Note that a Next.js dev warns that [this will greatly slow development](https://github.com/vercel/next.js/issues/12735#issuecomment-629404842).
153
153
* The current favicon implementation will probably not display correctly locally in Chrome (v94), but does display correctly in Firefox and Safari. Note that the favicon _does_ display correctly once deployed. Not sure why.
154
+
155
+
156
+
## Helpful tips
157
+
158
+
### Starting project is slow
159
+
160
+
If the npm install is running slow you can enable`mutagen`, to do this:
161
+
* In the `.ddev` folder create a file named: `config.mutagen.yaml`
162
+
* In the file place: `mutagen_enabled: true`
163
+
* Please Restart the project.
164
+
**NOTE**: if you run into an issue with problems starting please run `ddev delete -O`.
165
+
166
+
### Installing npm packages within ddev
167
+
168
+
If you would want to use `npm`, please do`ddev npm [package]`.
169
+
170
+
### If the application never starts
171
+
172
+
To verify that it is working please run: `ddev nextjs monit` and if it is not working as expected please try the following:
173
+
* Stop DDev, `ddev stop`
174
+
* Remove `node_modules` folder from the `services/app`
Copy file name to clipboardExpand all lines: services/app/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Forum One Next.js Starter App
1
+
# Forum One Next.js Starter App to run locally without ddev
2
2
3
3
This is a starter app for [Next.js](https://nextjs.org/) (bootstrapped with [`create-next-app`](https://github.com/vercel/next.js/tree/canary/packages/create-next-app)) that includes the following features:
0 commit comments