I integrated snowpack-plugin-nunjucks 0.0.3 in a brand new "core Web" project. My snowpack.config.js is quite simple:

/** @type { import("snowpack").SnowpackUserConfig } */
export default {
  devOptions: {
    open: "none",
  },
  env: {
    // ...
  },
  mount: {
    src: {
      url: "/",
    },
  },
  optimize: {
    bundle: true,
    minify: true,
    target: "es2018",
  },
  plugins: [
    "@snowpack/plugin-webpack",
    "snowpack-plugin-nunjucks",
  ],
};

Within src I've started to put together all the pieces, so I have an index.njk:

{% set title = "Home" %}

// Notice that files must be referenced from the project's root
{% extends "src/_layout.njk" %}

...

After I run Snowpack's build, I still see the Nunjucks templates (prefixed by _file_name.[ext], for instance, _layout.njk) being "generated" inside build.

I believe those files should be excluded, right? Only those .njk or .html files within src that aren't prefixed with _ should be processed and finally copied over into build.

Me again 👋🏻

I have the same simple project. Basically some .njk files in the project's root. When snowpack dev is executed the server starts correctly and so on, but when I browse over the exposed address (typically http://localhost:8080) the default entry point (index.html) is not recognized as HTML, but as application/octet-stream.

As a result, what I get is a prompt to download a file, which in turn, has the correct content (from index.html), but somehow it's not recognized automatically by the browsers as such.

Could it be that the integration with the plugin and Snowpack is not quite there yet, or do you think this is something that I might have misconfigured on my end — I'm quite new to Snowpack 😇