I’ve published a Vue package and now Vite fails to resolve its entry point. Likely due to configuration issues. Try this alternative setup:
import { initApp } from 'vue';
import MovingRay from 'vue-movingray';
import 'vue-movingray/dist/beam.css';
const appInstance = initApp(App);
appInstance.use(MovingRay);
hey, i had a similar issw fixed it by checking the main filed in package.json and adding an alias in vite config. sometimes cache issues also mess up the load so a restart might help
From my experience dealing with Vite and similar packages, the problem usually stems from the way module entry files are referenced. I had a comparable issue when developing my reusable component library. I discovered that double-checking the ‘main’ and ‘module’ fields in package.json was crucial. In my case, fixing capitalization mistakes and verifying that the file paths correctly pointed to the build output solved the problem. At times, a clean build and cache clear can make a big difference. It might help to review your build configuration and ensure consistency.
In my troubleshooting experience with Vite, I found that verifying the entry points specified in package.json is key, as even minor discrepancies can cause the module to fail to load, as seen in this case. The configuration in vite.config.js plays a significant role too. I encountered similar issues when mismatched aliases and entry definitions led to problems resolving the module. Double-checking these configurations and ensuring that the build output aligns with the published package often resolves the error.
hey, i had a similiar problm and fixed it by checking that vite alias exactly pointed to my build folder. also, a simple cache clear and server restart sometimes does the trick. sometimes its just a tiny misconfig causing the issue.
In my journey troubleshooting issues like these, I found that the problem sometimes stems from subtle differences in how Vite and webpack resolve module entries. I had a similar challenge with a Vue package where I had to explicitly export both ES and CommonJS versions in the package.json. This not only clarified the entry point for Vite but also ensured broader compatibility. In my case, updating the package configuration while verifying the output structure in the build log helped narrow down the problem. I suggest checking your build tool’s output for any unexpected path resolutions and adjusting accordingly.