【问题标题】:Angular(5) cli - Cloudinary - <cl-image> errorAngular(5) cli - Cloudinary - <cl-image> 错误
【发布时间】:2018-04-11 04:14:55
【问题描述】:

所以,

我正在尝试在我们的网站上实施 cloudinary 按照说明我有这个:

app.module

...
import { CloudinaryModule } from '@cloudinary/angular-4.x';
import { Cloudinary } from 'cloudinary-core/cloudinary-core-shrinkwrap';
...


const cloudinaryLib = {
  Cloudinary: Cloudinary
}
...
@NgModule({
  declarations: [AppComponent],
  imports: [
    CloudinaryModule.forRoot(cloudinaryLib, {cloud_name: 'mycloudname'})
    ...
  ]
  ...
});

然后在我看来我有

<cl-image public-id="id-to-the-asset"></cl-image>

在执行 ng serve 时出现错误

ERROR in Error at C:/DEVELOPMENT/app1/src/app/pages/a/a-page.component.html(10,3):  ("
  ></div>

  [ERROR ->]<cl-image public-id="site-assets/aaa"></cl-image>

  <div class="container">
")

任何想法为什么? 该错误没有说明原因

我正在使用

"@angular/core": "^5.0.0-rc.8",
...
"cloudinary-core": "^2.3.0",
"@cloudinary/angular-4.x": "^1.0.0",
...
"@angular/cli": "^1.5.0-rc.6",

另外,请注意,如果我从视图中删除 cl-image 并让 cli 构建页面,我会收到以下警告:

警告 ./node_modules/@cloudinary/angular-4.x/node_modules/@angular/core/@angular/core.es5.js 5659:15-36 严重依赖:依赖的请求是 表达 在 ImportLazyContextDependency.getWarnings (C:/DEVELOPMENT/app1\node_modules\webpack\lib\dependencies\ContextDependency.js:39:18) 在 Compilation.reportDependencyErrorsAndWarnings (C:/DEVELOPMENT/app1\node_modules\webpack\lib\Compilation.js:703:24) 在 Compilation.finish (C:/DEVELOPMENT/app1\node_modules\webpack\lib\Compilation.js:561:9) 在 applyPluginsParallel.err (C:/DEVELOPMENT/app1\node_modules\webpack\lib\Compiler.js:506:17) 在 C:/DEVELOPMENT/app1\node_modules\tapable\lib\Tapable.js:289:11 在 _addModuleChain (C:/DEVELOPMENT/app1\node_modules\webpack\lib\Compilation.js:507:11) 在 processModuleDependencies.err (C:/DEVELOPMENT/app1\node_modules\webpack\lib\Compilation.js:477:14) 在 _combinedTickCallback (内部/进程/next_tick.js:73:7) 在 process._tickCallback (internal/process/next_tick.js:104:9) @ ./node_modules/@cloudinary/angular-4.x/node_modules/@angular/core/@angular/core.es5.js @ ./node_modules/@cloudinary/angular-4.x/src/cloudinary-image-source.directive.js @ ./node_modules/@cloudinary/angular-4.x/src/cloudinary.module.js @ ./src/app/app.module.ngfactory.js @ ./src/main.ts @ multi webpack-dev-server/client?http://0.0.0.0:0./src/main.ts

警告 ./node_modules/@cloudinary/angular-4.x/node_modules/@angular/core/@angular/core.es5.js 5675:15-102 严重依赖:依赖的请求是 表达 在 ImportLazyContextDependency.getWarnings (C:/DEVELOPMENT/app1\node_modules\webpack\lib\dependencies\ContextDependency.js:39:18) 在 Compilation.reportDependencyErrorsAndWarnings (C:/DEVELOPMENT/app1\node_modules\webpack\lib\Compilation.js:703:24) 在 Compilation.finish (C:/DEVELOPMENT/app1\node_modules\webpack\lib\Compilation.js:561:9) 在 applyPluginsParallel.err (C:/DEVELOPMENT/app1\node_modules\webpack\lib\Compiler.js:506:17) 在 C:/DEVELOPMENT/app1\node_modules\tapable\lib\Tapable.js:289:11 在 _addModuleChain (C:/DEVELOPMENT/app1\node_modules\webpack\lib\Compilation.js:507:11) 在 processModuleDependencies.err (C:/DEVELOPMENT/app1\node_modules\webpack\lib\Compilation.js:477:14) 在 _combinedTickCallback (内部/进程/next_tick.js:73:7) 在 process._tickCallback (internal/process/next_tick.js:104:9) @ ./node_modules/@cloudinary/angular-4.x/node_modules/@angular/core/@angular/core.es5.js @ ./node_modules/@cloudinary/angular-4.x/src/cloudinary-image-source.directive.js @ ./node_modules/@cloudinary/angular-4.x/src/cloudinary.module.js @ ./src/app/app.module.ngfactory.js @ ./src/main.ts @ multi webpack-dev-server/client?http://0.0.0.0:0./src/main.ts

已编辑

我已降级到最新的 4.x angular 版本并且没有收到构建错误或警告...但我确实收到了

'cl-image' is not a known element:

所以还是不行

【问题讨论】:

  • 在运行 Angular 5 时使用名称中包含 Angular 4.x 的库似乎很冒险。
  • 是的,我也这么认为.... 将降级回稳定的 4x 版本,让我们看看
  • 你看到他们的CodePen了吗,可能有一些指点。

标签: angular angular-cli cloudinary


【解决方案1】:

它对我有用。我建议你需要

import * as cloudinary from 'cloudinary-core/cloudinary-core-shrinkwrap';

CloudinaryModule.forRoot(cloudinary,
  {
    cloud_name: 'ccloudd'
  } as CloudinaryConfiguration),

【讨论】:

  • 好吧,我降级了,它可以工作了...只是需要再次通过不同的设置...所以干杯!
猜你喜欢
  • 2018-09-02
  • 1970-01-01
  • 2018-01-29
  • 2018-04-20
  • 1970-01-01
  • 1970-01-01
  • 2022-01-06
  • 1970-01-01
  • 1970-01-01
相关资源
最近更新 更多