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
bug #917 Re-working dev-server and https detection (weaverryan)
This PR was merged into the main branch.
Discussion
----------
Re-working dev-server and https detection
Hi!
Fixes#903
If you pass `--https` at the command line, that overrides your `devServer.https` config. In webpack-dev-server v3, that wasn't a problem. But in v4, the certificate config was moved under `devServer.https`, which can now be an object. This meant that if you passed `--https` at the command line (which Encore previously required) but also set `devServer.https = { ... }`, that would be "re-set" back to `devServer.https = true` and your config would be lost.
The fix is to not require the `--https` flag and look at it or the user's config to determine if the dev-server is running in https.
Cheers!
Commits
-------
ee417f0 Re-working dev-server and https detection
thrownewError(`Cannot determine how to prefix the keys in manifest.json. Call Encore.setManifestKeyPrefix() to choose what path (e.g. ${suggestion}) to use when building your manifest keys. This is caused by setOutputPath() (${outputPath}) and setPublicPath() (${publicPath}) containing paths that don't seem compatible.`);
116
118
}
119
+
},
120
+
121
+
/**
122
+
* @param {RuntimeConfig} runtimeConfig
123
+
* @return {string|null|Object.public|*}
124
+
*/
125
+
calculateDevServerUrl(runtimeConfig){
126
+
if(runtimeConfig.devServerFinalIsHttps===null){
127
+
logger.warning('The final devServerFinalHttpsConfig was never calculated. This may cause some paths to incorrectly use or not use https and could be a bug.');
logger.warning(`Passing an absolute URL to setPublicPath() *and* using the dev-server can cause issues. Your assets will load from the publicPath (${this.webpackConfig.publicPath}) instead of from the dev server URL (${this.webpackConfig.runtimeConfig.devServerUrl}).`);
72
+
logger.warning(`Passing an absolute URL to setPublicPath() *and* using the dev-server can cause issues. Your assets will load from the publicPath (${this.webpackConfig.publicPath}) instead of from the dev server URL.`);
0 commit comments