Analyze if using NCP to copy folder is better

[gavinr]

Right now we're using copy in the rollup task, which I think runs each time a build happens:
1f1b08b#diff-ff6e5f22a9c7e66987b19c0199636480R47-R54

Another idea is to only copy the resources once, on npm-install, something like this:

Is this equivalent?
Is this better?

[jwasilgeo]

When doing a truly fresh clone + install, the "postinstall" in the screenshot won't quite cut it because the ./public/build folder doesn't exist yet and the copy will fail.

We need to prepend:

npm run build &&

Leading to this formula:

"npm run build && ncp ./node_modules/@esri/calcite-components/dist ./public/build/calcite-components"

[gavinr]

Since I logged this issue, I've simplified things a lot. This the diff with the svlete template: master...clean-svelte-template

Same issue still applies though - since we're using rollup-plugin-copy, when you save a change it takes about 10 seconds before the build is complete and the liveReload reloads the page :(

[gavinr]

I think using "rollup-plugin-copy" with copyOnce setting set to true is equivalent and simpler than the ncp solution. See here:
290d3ec#diff-6814bf77564b4f1c92f5861e184e28fe217c080a047fefa8b73a728f755ec45cR70