add a way to clear import cache for some file

[steve02081504]

it'll useful for hot reload codes

[dsherret]

The --reload flag?

[steve02081504]

The --reload flag?

no it'll reload hole server/app

wanna a way that you can just clear some file's import cache so you can reload that file without full restart.

// a.js
console.log("hi")

// b.js
await import("./a.js")
await import("./a.js") // no  output

delete require.cache["./a.;s"]

await import("./a.js")

[steve02081504]

https://github.com/steve02081504/fount/blob/master/src%2Fserver%2Fparts_loader.mjs
my repo relly needs this :)

[petamoriken]

Since ECMAScript specifies that ES modules are cached, unfortunately your proposal would violate the spec.

[petamoriken]

It is possible to load a module again as a separate module by using search params.

await import("./a.js");
await import("./a.js?2");

[steve02081504]

It is possible to load a module again as a separate module by using search params.

await import("./a.js");
await import("./a.js?2");

not work for my repo, just like this:

//a.js
import b from 'b.js'

// c.js
await import("./a.js");
await import("./a.js?2");// will not reload b.js, bad :(

[BlackAsLight]

Why do you need it to reload?

[steve02081504]

Why do you need it to reload?

user may update part/reload a same name part, and the js files in part may change.

[BlackAsLight]

Isn't that what the --watch flag is for?

[steve02081504]

Isn't that what the --watch flag is for?

no I don't wanna restart all codes :(

[petamoriken]

It's a dirty workaround, but you can use CommonJS require() for modules you want to purge the cache.

[steve02081504]

It's a dirty workaround, but you can use CommonJS require() for modules you want to purge the cache.

same issue as before:

//a.js
import b from 'b.js'

// c.js
require("./a.js");
require("./a.js");// will not reload b.js, bad :(

[petamoriken]

In the case of ConmonJS, delete require.cache[specifier] can be used.

[steve02081504]

In the case of ConmonJS, delete require.cache[specifier] can be used.

can we add an obj like import.cache?
I don't think the authors fount currently has would be convenient/willing to migrate to CJS, that's not that realistic.

[petamoriken]

We can't. If you want to make it happen, you should encourage TC39 to change the ECMAScript specification.

[0f-0b]

Why not use web workers? You can reload all modules by restarting the worker.

If code inside a buggy module goes into an infinite loop, you probably wouldn't want the entire app to freeze. Using workers you also get the ability to terminate ill-behaved code.

[steve02081504]

Why not use web workers? You can reload all modules by restarting the worker.

If code inside a buggy module goes into an infinite loop, you probably wouldn't want the entire app to freeze. Using workers you also get the ability to terminate ill-behaved code.

the parts of my repo offers entrypoints/files/functions, and they may share vars. web worker is hard for part writers to learn and understand, and hard for development and sharing values :)