dev server breaks plugin resolve/load()

[rkaw92]

Hi, I'm using snowpack-plugin-raw-file-loader - a plugin that turns raw files with designated extensions into loadable modules - in an application. The problem is, the loader works only with snowpack build - when I run snowpack dev, the imports result in 404 because the dev server thinks the translated .js files do not exist.

Example usage:

import pl from './translations/pl.ftl';
import en from './translations/en.ftl';

I've checked the source of the plugin, and it appears very simple - resolves the configured file extensions (in this case, [ '.ftl' ]) to [ '.js' ]. Its load function is executed properly in build mode - but not in dev! I've verified this by adding console.log statements to the load function and its config function. It looks like config() is executed always - in dev, and in build; however, load() is only ever executed in build but not in dev.

Another observation is that if I refer to the dev server via the original filename - so in my case http://localhost:8080/translations/pl.ftl - notice no .js mangling - then it does return the file with the proper (translated) contents, though as application/octet-stream.

Here's the file that is causing the problematic difference between dev mode and build mode: https://github.com/rkaw92/file-transfer/blob/main/public/l10n.js

[FredKSchott]

Happy to help! But, I can't reproduce. I can see the translations happening in dev:

[rkaw92]

Hmm... strange. Now that I test it with a fresh checkout and a new yarn install, it works exactly as you describe. This state is also impossible to reproduce from the repo I had this in (as development has moved forward). It appears to be a voodoo problem. Thank you for taking the time to try it out.

I think I'll make several more attempts to reproduce this - it definitely had been behaving as if the resolve feature was half-functional and persisted across multiple restarts of the dev server.