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
✘ [ERROR] Could not read from file: /MY_PROJECT_@_ALIAS_ROOT/dist/VPikaday.esm
node_modules/@ohmygodvt95/vue3-pikaday/index.js:1:21:
1 │ import VPikaday from "@/dist/VPikaday.esm";
╵ ~~~~~~~~~~~~~~~~~~~~~
I have defined the @ alias for my project. Vite is picking up the import VPikaday from "@/dist/VPikaday.esm"; and interpreting your @ alias as my alias. I wasn't aware that Vite does this for imports from node_modules. I tried to find best practice for whether or not to use aliases in the index.js entry point file but could not find much. Here is an issue report vitejs/vite#2290 in the Vite repo that didn't offer a workaround. Could you change the import to a simple relative path instead? The alias shouldn't be necessary in the entry point file.
I have not created an NPM package myself so let me know I am off base.
The text was updated successfully, but these errors were encountered:
I have defined the
@
alias for my project. Vite is picking up theimport VPikaday from "@/dist/VPikaday.esm";
and interpreting your@
alias as my alias. I wasn't aware that Vite does this for imports fromnode_modules
. I tried to find best practice for whether or not to use aliases in theindex.js
entry point file but could not find much. Here is an issue report vitejs/vite#2290 in the Vite repo that didn't offer a workaround. Could you change the import to a simple relative path instead? The alias shouldn't be necessary in the entry point file.I have not created an NPM package myself so let me know I am off base.
The text was updated successfully, but these errors were encountered: