-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Relative Javascript imports are apparently being cached by "name", not by the resolved path #253
Comments
Can you verify that this behaves differently with vanilla node?
On Thu, 1 Sep 2022 at 03:23, Samuel Tschiedel ***@***.***> wrote:
The reason I suspect this is a caching issue is that I'm able to bust it
with a query param on the import:
(:require ["./local-dep.mjs?t=0" :as i1])
(:require ["./local-dep.mjs?t=1" :as i2])
—
Reply to this email directly, view it on GitHub
<#253 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACFSBXMVWY4J6YK6GBS4FLV4AARLANCNFSM6AAAAAAQB4NT7Q>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
It does - hopefully I'm not glossing over relevant import/require details!
|
Makes sense, thanks. |
I hope to address this soon. |
Closed
Thank you! |
Published |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
version
platform
problem
Relative Javascript imports are apparently being cached by "name" not by the resolved path
repro
Given the following "project":
Running it gives
expected behavior
❯ nbb import_root.cljs Imported local dep 1 loaded import 1 core +Imported local dep 2 loaded import 2 core loaded import_root
Thanks for yet another incredible project! ❤️
The text was updated successfully, but these errors were encountered: