Matt
Matt
@saminton Did you manage to pass any data into the template component's props with that method?
Have I missed something in the Directus docs then? I thought migrations in Directus were rather manual.
Oh I did miss this, thank you for pointing it out!
I updated to v3.14.159 and the same thing still happens when the .db file is updated.
Unfortunately I wasn't able to create a repro on stackblitz or codesandbox. Instead, here's the reproduction in a git repo. To get the reproduction to work, you'll need to run...
@danielroe I've just tested this again, I reinstalled my node_modules and the issue still occurs. It might be a windows-only issue, I don't have a non-windows machine to this on...
I've think managed to reproduce the issue. The error was happening in our module. Inside our module.ts file we have the following line: `export * from "./runtime/composables/resources/generated/types";` This points to...
So it seems the issue is caused by specifying a file inside the runtime folder is causing the pnpm pack error. I moved the generated types out of the runtime...
I can confirm that moving the generated types out of the runtime directory fixes this issue.
Is there a reason why only the top level files in the `shared/utils` and `shared/types` folders are auto-imported, and not nested folders like `shared/foo` or `shared/utils/bar`?