Jason Aslakson
00003193df
Additional config options for hot reloader web socket connection ( #6083 )
...
* Additional config options for hot reloader web socket connection
* Apply suggestions from code review
Accepting suggested code changes
Co-Authored-By: jaslakson <jason.aslakson@americastestkitchen.com>
* updated README with websocket proxy options
* Fix test / cleanup port setting
* Always set proxy_path
2019-01-19 13:39:09 +01:00
Tim Neutkens
9ffd23eeef
Replace pages-plugin with loader ( #5994 )
...
* Remove unused argument
* Replace pages-plugin with loader
* Add loader-utils types
* Remove logs
* Bring back previous deposal behavior
* Remove console.log
* Remove webpack/utils as it’s no longer in use
* Remove hot-self-accept-loader
* Error Recovery tests
* Make hotSelfAccept a noop default loader
* Fix windows deleted/added
* Remove logging
* Remove unused variables
* Remove log
* Simplify entrypoint generation
* Don’t return the function
* Fix _app test
* Remove code that’s always true
* Move aliases to constants
* Use alias
* Join pages alias in reduce
* Default pages differently
* Loop over pages instead of manually defining
* Move entry generation into common function
* Update packages/next/build/webpack/loaders/next-client-pages-loader.ts
Co-Authored-By: timneutkens <tim@timneutkens.nl>
* Update packages/next/build/webpack/loaders/next-client-pages-loader.ts
2019-01-08 23:10:32 +01:00
JJ Kasper
ba8cb31a40
Added WebSocket arg to allow manually setting port ( #5963 )
...
Saw a reply on the original pull request that the WebSocket using a random port broke their set up so I added a `--websocket` or `-w` argument similar to the `-p` argument to allow manually setting this port also.
2019-01-01 01:07:10 +01:00
Tim Neutkens
6795f681ef
Make sure WebSocket server port is always detected ( #5894 )
2018-12-16 01:56:27 +01:00
JJ Kasper
af07611a63
Implement websockets based on-demand-entries ping ( #4508 )
...
Fixes #4495
Here's my approach for replacing the XHR on-demand-entries pinger #1364 #4495 . I'm not sure if this is the way everyone wants to accomplish this since I saw mention of using a separate server and port for the dynamic entries websocket, but thought this would be a fairly clean solution since it doesn't need that.
With this method the only change when using a custom server is you have to listen for the upgrade event and pass it to next.getRequestHandler(). Example:
```
const server = app.listen(port)
const handleRequest = next.getRequestHandler()
if(dev) {
server.on('upgrade', handleRequest)
}
```
2018-12-14 12:25:59 +01:00
Tim Neutkens
5d2250ac27
Remove unused functions ( #5832 )
...
Couldn't find a reference to these functions as next-server uses the renderToHTML directly.
2018-12-06 16:47:10 +01:00
Tim Neutkens
58f5dd297a
Add Typescript types for builds functions ( #5791 )
2018-12-03 14:18:52 +01:00
Radovan Šmitala
bf157015fb
Remove WriteFilePlugin ( #5541 )
...
It is native by webpack-dev-middleware 3.1.0 up
2018-11-02 19:47:56 +01:00
Max Fierro
2c343baeba
Fix issue with HMR not working ( #5544 )
...
Change the ignore patterns to ignore `.git/` folder.
Add Windows pattern matching for `.next/` and `.git/` folders.
Fixes #5429
2018-10-28 23:01:45 +01:00
Tim Neutkens
82d56e063a
next-server ( #5357 )
2018-10-02 00:55:31 +02:00
Tim Neutkens
b1c4f3aec4
Monorepo ( #5341 )
...
- Implements Lerna
- Moves all source code into `packages/next`
- Keeps integration tests in the root directory
2018-10-01 01:02:10 +02:00
