Handle .html files in a plugin

[marekmicek]

Hi,

Consider a plugin which defines:

resolve: {input: [".html"], output: [".js"] }

Unfortunately this doesn't seem to work. Snowpack dev server handles the .html files in a special way, which prevents them to be loaded in a plugin, or to be placed in src/ directory for that matter.

[FredKSchott]

Yup, .html is a special case since we use it to handle your top-level route. With the setting described above, the first page that you load will be converted to JS, and fail to load as HTML.

Can you describe your use-case more? If it makes sense, maybe there's a way for us to better support you.

[marekmicek]

Thank you for the response.

Basically I am trying to make this code work (it is used alongside angularjs):

import template from './template.html';

const component = { template };

It's actually returning template.proxy.js file with the content of index.html (which is the default) and mime type text/html.

I understand the way snowpack handles HTML for the direct browser request, but this is actually esm import so I would expect that it could be handled by a plugin and to be searched for inside the src/ directory instead of a public/.

[insign]

Not sure if helps but the way I found was to escape the string then set to a var, then export default string, in a file.js.