Hacker News Reader

Due to that caching, you still need some sort of preprocessor to digest the files and generate an import map. Third party modules also add some extra friction. I found that when I ended up pruning out all the edge cases, just bundling it ends up being less work anyway.

View on HN

> Due to that caching, you still need some sort of preprocessor to digest the files and generate an import map.

Why? I haven't needed import maps at all.

> Third party modules also add some extra friction

This is true, sometimes 3rd party JS requires you write a small ESM wrapper, etc, but I haven't found it to be too onerous

If you import a module by its path or URL, it is cached by that path. So if you update a file, browsers that have already pulled that module will get the old version. Getting around this needs some sort of digest. To import that file, you need to either use an import map to get the proper digested file or a preprocessor step to substitute the digested name into the importing module.

Reply on news.ycombinator.com