Making Cloudinary Angular compatible with Angular 5

[bjornharvold]

Was getting this error when trying to compile with Angular 5:

WARNING in ./node_modules/@cloudinary/angular-4.x/node_modules/@angular/core/@angular/core.es5.js
5659:15-36 Critical dependency: the request of a dependency is an expression
at ImportLazyContextDependency.getWarnings (/Users/crash/git/traveliko/traveliko-spa-administration/node_modules/webpack/lib/dependencies/ContextDependency.js:39:18)
at Compilation.reportDependencyErrorsAndWarnings (/Users/crash/git/traveliko/traveliko-spa-administration/node_modules/webpack/lib/Compilation.js:703:24)
at Compilation.finish (/Users/crash/git/traveliko/traveliko-spa-administration/node_modules/webpack/lib/Compilation.js:561:9)
at applyPluginsParallel.err (/Users/crash/git/traveliko/traveliko-spa-administration/node_modules/webpack/lib/Compiler.js:506:17)
at /Users/crash/git/traveliko/traveliko-spa-administration/node_modules/tapable/lib/Tapable.js:289:11
at _addModuleChain (/Users/crash/git/traveliko/traveliko-spa-administration/node_modules/webpack/lib/Compilation.js:507:11)
at processModuleDependencies.err (/Users/crash/git/traveliko/traveliko-spa-administration/node_modules/webpack/lib/Compilation.js:477:14)
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)
@ ./node_modules/@cloudinary/angular-4.x/node_modules/@angular/core/@angular/core.es5.js
@ ./node_modules/@cloudinary/angular-4.x/src/cloudinary.module.js
@ ./node_modules/@cloudinary/angular-4.x/index.js
@ ./src/app/app.module.ts
@ ./src/main.ts
@ multi webpack-dev-server/client?http://0.0.0.0:0 ./src/main.ts

[demiro]

yes, please... I'd like this as well, asap

[roeeba]

Hi @bjornharvold, @demiro. Our team is aware of this issue. We'll make sure to resolve this as soon as we can.

[bjornharvold]

Thank you! Make @eitanp461 work his magic :-)

[sangwin]

Is this issue fixed? I am getting same issue in Angular 5 project

[glauberramos]

I am getting the same error as well

[roeeba]

Hey guys, the issue hasn't resolved yet. While this isn't a trivial issue, we're aiming to deploy a fix in the next few months, though there's isn't a final ETA yet. We'll update here once we do have one.

[bjornharvold]

Hi @roeeba

Can you elaborate on the complexity of this issue? Upgrading from 4.4.6 to 5.0.1 was a painless affair for all our applications and 90% of our other 3rd party libraries were already compatible. The other 10% were updated within a couple of days. Looking at Angular 5's change log of breaking changes, there are really none that stand out.

Just waiting for Cloudinary now to be able to use all the new goodness with Angular 5. Having to wait "a few months" for this is not the answer I was hoping for.

Cheers

[sangwin]

I am facing the same issue, However This ng2-cloudinary Plugin helped me out.

[roeeba]

Hi, @bjornharvold. Our dev team are working on this issue. While it's not complex, we still can't commit on an ETA at the moment. We're doing our best to resolve this ASAP.

[sangwin]

@roeeba I still think a month is a lot more time to fix such an issue.