-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
[Bug]: webpack_bundle with supports_worker=True + run_js_devserver + ibazel = missing bundle files #126
Labels
bug
Something isn't working
Comments
jbedard
added a commit
that referenced
this issue
Nov 2, 2023
jbedard
added a commit
that referenced
this issue
Nov 2, 2023
jbedard
added a commit
that referenced
this issue
Nov 2, 2023
jbedard
added a commit
that referenced
this issue
Nov 3, 2023
jbedard
added a commit
that referenced
this issue
Nov 3, 2023
jbedard
added a commit
that referenced
this issue
Nov 6, 2023
jbedard
added a commit
that referenced
this issue
Nov 8, 2023
jbedard
added a commit
that referenced
this issue
Nov 8, 2023
jbedard
added a commit
that referenced
this issue
Nov 8, 2023
jbedard
added a commit
that referenced
this issue
Nov 8, 2023
thesayyn
pushed a commit
that referenced
this issue
Nov 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
If you run new example from #125 using ibazel, made some changes and re-run ibazel, .css and .js files will be missing on next ibazel invocation
Version
Development (host) and target OS/architectures:
bazel 6.4.0
macOS 13.6 (22G120)
How to reproduce
Using #125:
cd e2e/loaders
ibazel run :devserver
open http://127.0.0.1:8080/html/
(and open DevTools in browser)Hello webpack
h1
for example)ibazel
processibazel run :devserver
againSee two pictures above. 1 — first
ibazel
run. 2 — secondibazel
run (demonstrates the issue)Workaround:
bazel clean
Any other information?
No response
The text was updated successfully, but these errors were encountered: