-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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(Worker): Not loading latest version of specified script #6116
Comments
Thanks for the report. I guess it's related to our module cache - it should be bypassed for dynamic loads (Worker constructors and dynamic imports). @bartlomieju what do you think? |
I just tried the reproduction with 1.5.2 and it works as expected. |
Sorry - I didn't understand the example correctly. This is still a bug. |
Fixes #4743 Closes #5253 Fixes #5631 Fixes #6116 Co-authored-by: Bartek Iwańczuk <[email protected]> Co-authored-by: Luca Casonato <[email protected]>
Fixes denoland#4743 Closes denoland#5253 Fixes denoland#5631 Fixes denoland#6116 Co-authored-by: Bartek Iwańczuk <[email protected]> Co-authored-by: Luca Casonato <[email protected]>
This bug appears to have come back. I setup the steps to reproduce from the OP today running Deno v1.27.0 on Windows and did not get the expected result. After changing the text in script.ts and saving the file Deno continued to print the original string. I also tried closing the worker from itself ( |
@dev-nicolaos can you please open a new issue? |
@bartlomieju I've opened #16503 |
Steps to reproduce
script.ts
with the contentconsole.log('hello')
.main.ts
with the following content:deno run --allow-read main.ts
.script.ts
toconsole.log('bye')
and save it.Expected result
The subsequent log of
deno run --allow-read main.ts
should bebye
.Actual result
After step 4, the subsequent log of
deno run --allow-read main.ts
is stillhello
.Environment:
Is this introduced lately?
No, this is happening on every version of Deno since
v1.0.0
untilv1.0.5
.Current workaround
Refer https://stackoverflow.com/a/41790024/6587634
The text was updated successfully, but these errors were encountered: