Dynamic routes in public folder

[meigo]

Is there any reason behind including dynamic route folders (as [slug] with index-[hash].js in template project) to public folder on production build, I think these are not used in production at all?

[meigo]

Removed source maps from production with

output: {
      ...
      sourcemap: watch && true,
}

But negating pattern seems not to work when square brackets are present in folder name with rollup-plugin-copy (or rollup-plugin-glob) and these folders are copied over to public folder. Actually making a duplicate in public root.

copy({
  targets: [
    ...
    { src: ['build/server/**/*', '!**/*.js', '!**/*.js.map'], dest: 'public' }
  ],
}),

As for template only css files were needed from build/server replaced copy target line with

{ src: 'build/server/**/*.css', dest: 'public' },