Vite cannot resolve entry for package "@cloudinary/html" about frontend-frameworks HOT 19 CLOSED

It's the same thing in @cloudinary/react. The pacakge.json claims the main entry file dist/index.js, but in the package published, the compiled files are in the pckage's root, there is no dist folder. Either the main path is wrong or the build should contain a dist folder with compiled js.

from frontend-frameworks.

@ctwheels Thanks, this will be released promptly (Sunday)

It was fixed in #136

from frontend-frameworks.

@ctwheels Thank you for the information we can indeed see the issue. We'll work on fix and update here on this thread once it is resolved.

from frontend-frameworks.

Thanks @ljonya
Can you please provide a minimal repo that reproduces this issue?

from frontend-frameworks.

@patrick-tolosa Here's the repo: https://github.com/ljonya/my-svelte-app
However, the problem is so obvious that the repo is unlikely to help.

from frontend-frameworks.

Thanks for the additional details.

We're in the middle of finishing the work on this project to release it as an official release, and we might not get to resolving this issue in this beta version.

We'll update this thread in any case once this is resolved (Either by an official release, or a bug fix on this beta version)

from frontend-frameworks.

@patrick-tolosa are there any updates on this? Looking to use it with sveltekit + vite and getting same issue, same fix.

from frontend-frameworks.

No immediate date @ctwheels , the initial release of this package will contain React and Angular, and following releases will include Svelte and Vue.

from frontend-frameworks.

We've merged fix to this issue and we'll release a patch in the next few days.

from frontend-frameworks.

@ljonya a fix for this issue was released:) Please let us know if you encounter any other issues.

from frontend-frameworks.

Closing for now, please reopen if still relevant.

from frontend-frameworks.

@patrick-tolosa this issue still exists for @cloudinary/html.
If you look at the changes that were made, only the React package was updated: https://github.com/cloudinary/frontend-frameworks/pull/131/files
The changes were not made for the html package (which affects Vite, Svelte, and other frameworks).

Image below of the package.json; which still contains the dist path.

from frontend-frameworks.

@ctwheels please see the latest release.

from frontend-frameworks.

@strausr thank you - I do see that it's now updated. I'm getting the following error now though. Any idea how to resolve this?

X [ERROR] [plugin vite:dep-scan] Failed to resolve entry for package "@cloudinary/html". The package may have incorrect main/module/exports specified in its package.json: Failed to resolve entry for package "@cloudinary/html". The package may have incorrect main/module/exports specified in its package.json.

from frontend-frameworks.

@ctwheels Thanks for the update. I'm unable to reproduce this on my end. Can you please share with me the reproduction steps?

Could you also provide the versions of the Cloudinary packages you're using?

from frontend-frameworks.

@strausr I have a sample here: https://github.com/ctwheels/cloudinary-html-vite-issue
It's a sveltekit project I just initialized and setup as a small sample of my existing project.
I'm using pnpm and netlify but use any package manager/utility and you get the same error.

Using @cloudinary/html version 1.2.0 and can confirm the links are updated (no longer have dist in them).

This line imports the Image component and anything else that's needed for Cloudinary image to be displayed.
This directory is where the Cloudinary image component exists in the project.
Edit this line with the name of your cloud instance for Cloudinary.

Let me know if you have any questions.

from frontend-frameworks.

@ctwheels Please see the latest release

from frontend-frameworks.

@strausr still getting same error on v1.2.2.

ERROR: [plugin: vite:dep-scan] Failed to resolve entry for package "@cloudinary/html". The package may have incorrect main/module/exports specified in its package.json: Failed to resolve entry for package "@cloudinary/html". The package may have incorrect main/module/exports specified in its package.json.

Although, it does load now in some instances, but it always reports this error.

I also updated my repo to include the new release - you can pull that in again and run the dev script to test.

from frontend-frameworks.

@ctwheels Thanks for the informarion. We'll take a look and update you with our findings

from frontend-frameworks.