Using `web_accessible_resources` to copy the official i18n `_locales` folder removes the `_` about chrome-extension-tools HOT 8 CLOSED

Whoops, that's a problem! We need to support localization better.

You might take a look at a Rollup plugin to copy this folder. I don't think _locales needs to be web accessible, so it should work. My favorite one is rollup-plugin-copy2, since it works well with rollup-plugin-zip, which makes releases a breeze.

from chrome-extension-tools.

Thanks, I've done something similar for the time being 👍🏼

from chrome-extension-tools.

Hi @rick-stevens! We've added _locales support on the beta release npm i rollup-plugin-chrome-extension@beta -D . Could you give it a can test run on your MV2 extension? 🧐 (MV3 support is not finished yet).

It should work without adding the _locales in the web accessible resources folder 😄

from chrome-extension-tools.

That's great! I've temporarily moved to a custom Vite stup to support MV3, so I can't easily test in my current project. But the reproduction steps are quite simple and not related to a specific project structure. Happy that works now. Awaiting MV3 support! 🙏🏼

from chrome-extension-tools.

@rick-stevens Have you been able to get HMR working with vite? 🤔 We'll be working on the reloader next week and I wanted to know what others are using for reloading in all the different contexts (background, content scripts, etc) during development.

from chrome-extension-tools.

i tried to copy the transalation folder, it's creating the folder for sec, but then it's removed somehow. any idea how to resolve this?

import copy from 'rollup-plugin-copy'

 copy({
      targets: [
        { src: 'src/_locales/**/*.json', dest: 'dist/_locales' },
      ]
    }),

from chrome-extension-tools.

resolved with :

import execute from 'rollup-plugin-execute'

 execute('yarn postbuild && yarn copy')

where running cp cli commands

from chrome-extension-tools.

@rick-stevens Have you been able to get HMR working with vite? 🤔 We'll be working on the reloader next week and I wanted to know what others are using for reloading in all the different contexts (background, content scripts, etc) during development.

Sorry, I havent. I went for quick and dirty:

{
  "scripts": {
    "build:background": "vite build --config background.vite.config.js",
    "build:content": "vite build --config content.vite.config.js",
    "build:options": "vite build --config options.vite.config.js",
    "build": "rimraf dist && concurrently yarn:build:*"
  }
}

And used the /public folder for the manifest, locales, icons and CSS.

from chrome-extension-tools.