"rollup-plugin-copy" not work on dev mode

[onsummer]

Same aims as #1231, I want to copy some files from 'node_modules/@arcgis/core/assets' to 'public/assets', here is my vite.config.js:

import { defineConfig } from 'vite'
import vue from '@vitejs/plugin-vue'
import copy from 'rollup-plugin-copy'

export default defineConfig({
  plugins: [
    vue(),
    copy({
      targets: [
        { src: "node_modules/@arcgis/core/assets", dest: "public/assets" }
      ],
      hook: 'writeBundle'
    })
  ]
})

Here are my deps:

{
  "dependencies": {
    "@arcgis/core": "^4.19.3",
    "vue": "^3.0.5"
  },
  "devDependencies": {
    "@vitejs/plugin-vue": "^1.2.2",
    "@vue/compiler-sfc": "^3.0.5",
    "rollup-plugin-copy": "^3.4.0",
    "vite": "^2.3.3"
  }
}

It only work on prod mode. That is to say, when I run yarn build && yarn serve, open http://localhost:5000, the app run all well, but however, when I run yarn dev, the app access some resources in assets folder will report 404:

[onsummer]

I found a compromise method: Manually copy node_modules/@arcgis/core/assets folder to public/ folder in advance, it works on dev mode. But it is not flexible at all.
What should I do? Thanks.

[CHOYSEN]

Try changing the hook to buildStart?

[onsummer]

谢谢，待会试试
tks, I will try later

[KonnorRogers]

@CHOYSEN I tried using both buildStart and options build hooks but it doesnt write to disk with the dev server but works perfectly when I build the full bundle.

[FezVrasta]

Did anyone ever figure out a solution? I suppose the dev server serves files from a different folder, how can I know its path?

[XiangYyang]

Did anybody knows how to solve? I tried hook: "writeBundle" and hook: "buildStart ", and neither work.

However, they work well when I use npm run build.

[gauravjhs]

Please check #6696 for a possible solution

[ButuzGOL]

Workaround to use twice

for dev
dest: 'resources/locales',
hook: 'buildStart',

for prod
dest: 'dist/resources/locales',
hook: 'writeBundle',

[HatemMn]

Thank you ! this worked

It seems like we should avoid to "mention" the dist folder during the usage of the dev server ...