✨ Create server-rendered universal JavaScript applications with no configuration
MIT License
Bot releases are hidden (Show)
Published by fivethreeo over 2 years ago
Published by fivethreeo over 2 years ago
Published by fivethreeo almost 3 years ago
Published by fivethreeo almost 3 years ago
Published by fivethreeo almost 3 years ago
Published by fivethreeo almost 3 years ago
Published by fivethreeo almost 3 years ago
Published by fivethreeo almost 3 years ago
Published by fivethreeo almost 3 years ago
Published by fivethreeo almost 3 years ago
Huge thanks to @nimaa77 for helping!
Published by fivethreeo almost 3 years ago
Published by fivethreeo almost 3 years ago
Published by fivethreeo almost 3 years ago
packages/razzle/package.json
to allow webpack-dev-server
v4 as a peerDependency - Updated createConfigAsync.js
to move the hot: true
flag into just the v3 config since it is on by default for v4 removing the following warning: [webpack-dev-server] "hot: true" automatically applies HMR plugin, you don't have to add it manually to your webpack configuration.
: c87ba641095a90d74ecc175fc7c6782b1385a6f7devServerMajor.js
to razzle-dev-utils
that refactors the detection of the webpack-dev-server
version in a manner similar to webpackMajor.js
- Updated webpackHotDevClient.js
to use devServerMajor.js
to pickup the properly cased createSocketUrl
- Hopefully this approach won't break things like the change that was made previously that ended up getting reverted - Updated createConfigAsync.js
to use razzle-dev-utils/devServerMajor
for the webpack-dev-server
version as well as: - Restored hot: true
to the common devServer
config and instead only explicitly adding the HMR
to the plugins for v3 to avoid the following warning: [webpack-dev-server] "hot: true" automatically applies HMR plugin, you don't have to add it manually to your webpack configuration.
- Updated start.js
script to include devServerMajor.js
so that v4 will start/stop
the client dev server rather than listen/close
used for v3 - Also added port
into the copied devServer
config to allow start()
to work properly: 2a362ae8d5e8d7c898aba5ecfec8ef1f7b00d35cconsole.error()
: de1903e518ee18a55566c27bd6366b817d077399createSocketUrl
variable to happen before it is used: 2cd80756a869425745f37270646c7b08dab42dd4verbose: verbose
down to verbose
during object declaration: e03de4858ad81cfcf5479b24b1785f9ee4f8a9afstart()
and stop()
with a generic error handler: 8c9045545491c7af8d79f50336a8b1c098c1f30ePublished by fivethreeo about 3 years ago
Published by fivethreeo about 3 years ago
Published by fivethreeo about 3 years ago
package.meta.json
and packages/razzle-dev-utils/package.json
to allow for v3 and v4 of webpack-dev-server
- Updated defaultOptions.js
to add a new default option: enableDevServerV4: false
- Updated createConfigAsync.js
to build the correct devServer
config for v3 or v4 based on the enableDevServerV4
option - Added a new with-webpack-dev-server-v4
example: c3625eb1e19886187bcfc673d5beb30f512092e3webpack-dev-server
from its package.json
- Updated with-webpack-dev-server-v4
the README.md
and razzle.config.js
files to throw an error if not using version 4: 48356b2f63164b18bf95d18d7b1c8b8edd098f47require()
up to the top and collecting common options and Object.assign()
ing the v3 and v3 specific ones: 58040702ccad4ee88b85a0929328293e2082d5d4devServerMajorVersion
up to the top of the file: 51b7c29f2852cda753d4c398a2e7716aa60af83cwith-fastify
example and implementation: 5ba7e96940ecc9191109ac5d39445796c87914d3Published by fivethreeo about 3 years ago
Published by fivethreeo over 3 years ago
Published by fivethreeo over 3 years ago