You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is just a minor bug I just noticed, but maybe this has some bigger consequences (why would esbuild use the lower case name at all? Even for caching, my file system is case sensitive)
I added an import to a non-existant file EditRawResponse.svelte. Then I added the file. Esbuild will then log the added file name as lower case. Editing the file and saving it again logs the correct file name. This is on 0.14.51
✘ [ERROR] Could not resolve "./EditRawResponse.svelte"
components/FlowDetails.svelte:62:28:
62 │ import EditRawResponse from './EditRawResponse.svelte';
╵ ~~~~~~~~~~~~~~~~~~~~~~~~~~
2 errors
[watch] build finished
[watch] build started (change: "components/editrawresponse.svelte") <============== Why is this lower case?
[watch] build finished
[watch] build started (change: "components/EditRawResponse.svelte")
The text was updated successfully, but these errors were encountered:
I think I can fix this aesthetically. But it's important to know that internally esbuild uses case-insensitive file names on all platforms. This is for cross-platform portability since case-insensitivity is common on both macOS and Windows. It would be bad for a build on a case-sensitive file system to suddenly fail on a case-insensitive file system. For example, this prevents CI from passing on Linux only for the build to fail on macOS.
This is just a minor bug I just noticed, but maybe this has some bigger consequences (why would esbuild use the lower case name at all? Even for caching, my file system is case sensitive)
I added an import to a non-existant file
EditRawResponse.svelte
. Then I added the file. Esbuild will then log the added file name as lower case. Editing the file and saving it again logs the correct file name. This is on 0.14.51The text was updated successfully, but these errors were encountered: