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
The dev server default output, upon starting up, indicates that a server is running on localhost at a specific port. Because this server is meant to run alongside a separate WordPress install (usually either Vagrant with Chassis or Docker with Altis Local Server), this can be confusing because it seems to imply your site could be accessible from the Webpack server, when Webpack is solely responsible for providing the built bundled files.
Sample output:
> webpack-dev-server --config .config/webpack.config.dev.js
ℹ 「wds」: Project is running at https://localhost:9090/
ℹ 「wds」: webpack output is served from https://localhost:9090/content/mu-plugins/my-plugin/build/
ℹ 「wds」: Content not from webpack is served from /hm/projects/my-project
It would be good to see if we can add a logging message indicating that the main site should still be accessed via the underlying WP dev environment hostname.
The text was updated successfully, but these errors were encountered:
The dev server default output, upon starting up, indicates that a server is running on localhost at a specific port. Because this server is meant to run alongside a separate WordPress install (usually either Vagrant with Chassis or Docker with Altis Local Server), this can be confusing because it seems to imply your site could be accessible from the Webpack server, when Webpack is solely responsible for providing the built bundled files.
Sample output:
It would be good to see if we can add a logging message indicating that the main site should still be accessed via the underlying WP dev environment hostname.
The text was updated successfully, but these errors were encountered: