Babel cache#1369
Conversation
| "dev": "next", | ||
| "build": "next build", | ||
| "clean": "rimraf .\\node_modules\\.cache", | ||
| "build-dev": "npm run clean && next build --env=development", |
There was a problem hiding this comment.
why not simply
"build-dev": "npm run clean && next build",
"build-prod": "npm run clean && NODE_ENV=production next build"
?
There was a problem hiding this comment.
maybe we need to pass additional parameters like instance (we need to pass 2 params)
There was a problem hiding this comment.
Then can just add another env var.
IMHO that's unrelated to what the example is trying to convey. There's no need for command-line-args to get universal config working.
| "react-dom": "^15.4.2" | ||
| }, | ||
| "devDependencies": { | ||
| "command-line-args": "^4.0.2", |
There was a problem hiding this comment.
I didn't understand why this package was needed
There was a problem hiding this comment.
I think that this package makes params from command line easy to collect
|
@arunoda the babel-loader caching issue here makes me think we should clear |
|
@timneutkens then in development, it won't get used. In the deployment we could clean it, but I rather let it to be done by the user. |
|
@arunoda yeah lets document the way someone has to clear the cache instead of flushing it ourselves. |
|
Closing this in favor of #1432. |
5 participants
Fix problem with babel cache problem, ability to switch versions with command line args