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
When we eventually move away from using .env configuration files, we'll want to ensure that the webpack.dev.config.js is able to provide the port number from env.config.js.
Currently, the port number for the devserver is determined here, which means that on npm run start it will only ever look at the process.env object for the PORT or it will default to 8080, which isn't ideal for developing with multiple repos running that don't have .env.* files anymore.
To fix this, we would need to figure out a way to bring the port number from env.config.js during runtime in webpack.dev.config.js or require all repos that now use env.config.js to modify the port assignment in their customized webpack dev config.
Example of an MFE with a .env.development AND env.config.js
jsnwesson
changed the title
webpack.dev.config.js should be able to refer to port number in env.config.js if providedwebpack.dev.config.js should be able to refer to use port number in env.config.js if provided
Feb 7, 2024
When we eventually move away from using
.env
configuration files, we'll want to ensure that thewebpack.dev.config.js
is able to provide the port number fromenv.config.js
.Currently, the port number for the devserver is determined here, which means that on
npm run start
it will only ever look at theprocess.env
object for the PORT or it will default to 8080, which isn't ideal for developing with multiple repos running that don't have.env.*
files anymore.To fix this, we would need to figure out a way to bring the port number from
env.config.js
during runtime inwebpack.dev.config.js
or require all repos that now useenv.config.js
to modify the port assignment in their customized webpack dev config.Example of an MFE with a
.env.development
ANDenv.config.js
The text was updated successfully, but these errors were encountered: