Best practice for managing env's?

[areohbe]

Is there a recommended pattern for support an env specific manifest.json. For example, if I wanted to use a different icon for dev/beta from production. Is this kinda thing supported?

[jacksteamdev]

You can extend the manifest using options.extendManifest. This option will merge the supplied object with the manifest data.

export default {
  ...rollupConfig,
  plugins: [
    chromeExtension({
      extendManifest: {
        icons: { ... } // Overwrite just the icons object
      }
    }),
    ...plugins
  ],
}

I'd like to support this better in the future! Right now the manifest file name is validated as manifest.json, which is probably too strict. Would be nice to support other file formats too, like TS.

[areohbe]

Ah! Not sure how I missed that. Good enough for my use case.

[jacksteamdev]

@areohbe You might be interested in #94 and the latest beta release. It adds support for manifest files in TypeScript (and therefore env's)!

[areohbe]

@jacksteamdev very cool! Thanks for all the work. It made developing a Svelte-powered Chrome Extension a real breeze. It's pretty specific to particular way in which I use Gmail, but it's always nice to see your work out in the wild if you'd like to check it out. https://github.com/areohbe/power-gmail

[jacksteamdev]

Thanks for sharing! It is nice to see your work being used 👍