ERROR in ./.nuxt/cloudinary/plugin.client.js
See original GitHub issueI’m on Nuxt version 2.11.0
and I get this error:
ERROR in ./.nuxt/cloudinary/plugin.client.js Module not found: Error: Can't resolve './cloudinary-api' in '/app/.nuxt/cloudinary'
Looking at my .nuxt
folder, and I see the structure like this:
There is an issue with the cloudinary-api
js file being placed in the root rather than the cloudinary
folder
Issue Analytics
- State:
- Created 3 years ago
- Comments:5
Top Results From Across the Web
Build fail after updating to v1.2.0 · Issue #133 - GitHub
I've been using cloudinary-vue v1.1.2 in a nuxt.js project which has been working fine. ... node_modules/.cache/nuxt/client.js ERROR in .
Read more >Cloudinary Instance
This module globally injects $cloudinary instance. You can access it anywhere using this.$cloudinary (within a component), or context.
Read more >@nuxtjs/cloudinary - npm
Cloudinary module for Nuxt. Latest version: 1.0.3, ... Start using @nuxtjs/cloudinary in your project by running `npm i @nuxtjs/cloudinary`.
Read more >[Solved]-Error using @Nuxt.js/Cloudinary module for Media ...
Uploading assets is only possible with a Programmable Media account. The course is a paid course so I can't access its content but...
Read more >Ask Question - Stack Overflow
Error using @Nuxt.js/Cloudinary module for Media Optimization "You don't have sufficient permissions to access this endpoint".
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Ok, there is a change in convention from 2.13 onwards, where
fileName
becomesfilename
😅. A fix will be on the way 😃@genu I tried Nuxt < 2.11 and it did happen. So yeah, it looks like something about the Nuxt API changes for earlier version. I will add a minimum Nuxt version requirement for now and see if we can add a fix without too much hassle 😃. Thanks