Replies: 1 comment
-
So I just did some more tests. Apparently it is the whitespace character in the path causing the trouble ( |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello everyone,
it’s really hard to find anything regarding this problem, although I guess I’m not the only one having it. I’m working on a Mac and recently started using iCloud Drive to have a remote copy of my files, being able to sync between devices and so on. It’s tightly integrated with macOS and I’m more or less happy with its simplicity.
BUT: when having SvelteKit projects stored in a directory that is synced to iCloud Drive all error messages during development show incorrect paths. Instead of telling me which
.svelte
file is the source of the problem, I get the path to a.js
chunk that’s not useful at all. As soon as I move the project out of the cloud the correct paths are back.What’s interesting is that building the project works perfectly—so there is no real problem with having the project residing in the cloud. It’s only the error messages that get the path wrong. (macOS uses some unknown magic to give the impression that iCloud drive folders are regular folders in the Finder. As soon as you start accessing them programmatically you notice that that’s not true.)
I’m not sure where to start debugging this. Is it SvelteKit, Vite.js, Rollup.js or Node.js getting lost in the cloud?
The errors I’m seeing look something like this:
After moving it out of the cloud, the errors look like this:
Did anybody have the same problem and find a solution? All trouble regarding coding projects stored using iCloud Drive being discussed on the internet have to do with the
~
and whitespace characters being used in the path. But they don’t seem to be the problem here, since building the project works as expected.Beta Was this translation helpful? Give feedback.
All reactions