Changing the file extension after build

[johnagan]

I'm confused at the mechanism for changing file extensions on build. I have two filetypes I'm attempting to build pug and pcss. Naturally, I would expect pug to output as html and pcss to css.

1. I first attempted to do this in the snowpack.config.json. Both compiled properly, but output had the src extensions:

{
  "scripts": {
    "build:pcss": "postcss",
    "build:pug": "pug",
  }
}

2. I attempted to write my own plugin with a build script, but this didn't give me the option to change extensions.

3. I attempted to write my own loader like the docs describe, but I wasn't sure on how to call a loader since it wasn't an accepted script-type.

4. Then I found this gem in the code. So I attempted various versions of build:pcss->css and build:pug->html, but it never worked.

---

I don't want to use the build command to call the CLI and specify input/output files, which seems like the only resort.

[FredKSchott]

Hey @johnagan, we're about to release an update to our plugin interface with some enhancements to specifically support this behavior. Previously, custom build mapping wasn't really supported outside of our internal allow-list.

If you feel comfortable writing your own Snowpack plugin:

• You can try out a pre-release version: npm install snowpack@^2.7.0-pre.1
• With our latest pre-release docs here: https://snowpack-git-plugin-docs.pikapkg.vercel.app/plugins

If you want to keep the simplicity of using the CLIs:

• this will still be supported, but isn't yet documented!
• hang tight, we'll have that for you in the next day or so.