Rename does not let me alter the folder to which the file is written. #70
Comments
|
Update: I believe I was able to get this to work using the following configuration. The notable change was to set flatten back to true: import { defineConfig } from "vite";
import laravel from "laravel-vite-plugin";
import copy from "rollup-plugin-copy";
import path from "path";
// ! TECH DEBT: TTLT-1839
export default defineConfig({
plugins: [
laravel({
input: [
"resources/js/app.js",
],
refresh: true,
}),
copy({
flatten: true,
targets: [
{
src: "resources/assets/**/*",
dest: "public",
rename (name, extension, fullPath) {
return fullPath.split(path.sep).slice(2).join(path.sep);
},
},
{
src: "resources/docs/**/*",
dest: "public",
rename (name, extension, fullPath) {
return fullPath.split(path.sep).slice(2).join(path.sep);
},
},
],
verbose: false,
}),
],
}); |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have tried various rename suggestions in order to remove the top level folder from being copied over, but rename only seems to affect the filename itself, and not the destination folders.
For example:
My goal is to copy the content into
public, notpublic/assets(which is the default behavior). Various issues in the repo recommend using rename to achieve this. Unfortunately this only works at the first level, not in multi-level globs with nested directories. You can see by the output that nested folders are repeated, instead of traversing up a folder:Up until
resources/assets/site.webmanifest → public/site.webmanifest [R]everything is correct, after that everything is incorrect, because it once again includes theassetssubfolder.(I tried without "../" and that didn't work at all.)
Any suggestions on how to address this?
Possibly related issues:
#32
#56
The text was updated successfully, but these errors were encountered: