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
Webpack dev server doesn't work with Codenvy. There are no error messages, and I'm still learning how to use Codenvy. Any help will be deeply appreciated.
Reproduction Steps:
I currently run this command on a static app project in Codenvy using a command:
webpack-dev-server --inline --hot
I get the following response from the terminal:
command: cd /projects/CAAS && npm run dev
preview:node15.codenvy.io:33373
[email protected] dev /projects/CAAS
webpack-dev-server --inline --hot
Project is running at http://localhost:8080/
webpack output is served from /dist/
404s will fallback to /index.html
(node:2768) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see webpack/loader-utils#56
parseQuery() will be replaced with getOptions() in the next major version of loader-utils.
Codenvy version:
5.4.1
OS and version:
Chrome OSX
Docker version:
???
The text was updated successfully, but these errors were encountered:
Webpack dev server doesn't work with Codenvy. There are no error messages, and I'm still learning how to use Codenvy. Any help will be deeply appreciated.
Reproduction Steps:
I currently run this command on a static app project in Codenvy using a command:
webpack-dev-server --inline --hot
I get the following response from the terminal:
command: cd /projects/CAAS && npm run dev
preview:node15.codenvy.io:33373
Project is running at http://localhost:8080/
webpack output is served from /dist/
404s will fallback to /index.html
(node:2768) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see webpack/loader-utils#56
parseQuery() will be replaced with getOptions() in the next major version of loader-utils.
Codenvy version:
5.4.1
OS and version:
Chrome OSX
Docker version:
???
The text was updated successfully, but these errors were encountered: