-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot GET /bundle.js
with browser production build
#12962
Labels
critical
critical bugs / problems
Comments
1 task
1 task
Thanks @perrinjerome for raising this issue and thank you very much @msujew for the analysis and fix! I've tested and approved #12964. |
planger
added a commit
to eclipsesource/theia
that referenced
this issue
Sep 30, 2023
Currently we don't seem to have any automated test that verifies whether the production build works as expected. For a recent issue and its root cause, which remained unrevealed by the CI, see eclipse-theia#12962 Contributed on behalf of STMicroelectronics Change-Id: Ia2fdb54873344e5d0da12522441a649b6b90bdac
planger
added a commit
that referenced
this issue
Nov 16, 2023
Currently we don't seem to have any automated test that verifies whether the production build works as expected. For a recent issue and its root cause, which remained unrevealed by the CI, see #12962 Contributed on behalf of STMicroelectronics
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Description:
I have been using a theia browser application very similar to examples/browser, where unlike examples/browser which uses
theia build
in development mode (see below), I just used thetheia build
with default mode, which is production.theia/examples/browser/package.json
Line 65 in bb7cdbb
It was working fine with theia 1.35.0 but when I tried to update to 1.42.0 I have an error when opening http://localhost:3000/ with the browser because
/bundle.js
serves an error pageCannot GET /bundle.js
.Steps to Reproduce:
After cloning theia repository:
Additional Information
I have bisected that this comes from 45a0953 which seems unrelated, but maybe triggers something with webpack in production mode. I have no idea why this would happen, but when reverting part of this commit by applying this patch on top of master,
bundle.js
is generated again:I am not suggesting doing this change, just mentioning this in case it helps in tracking down the issue.
The text was updated successfully, but these errors were encountered: