-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uncaught Error: moduleId should be a string in "Ng2SliderComponent". #24
Comments
kalandher
changed the title
Uncaught Error: moduleId should be a string in "Ng2SliderComponent". See https://goo.gl/wIDDiL for more information. If you're using Webpack you should inline the template and the styles, see https://goo.gl/X2J8zc.componentModuleUrl @ VM21418:862CompileMetadataResolver.getNonNormalizedDirectiveMetadata @ VM21418:214CompileMetadataResolver._loadDirectiveMetadata @ VM21418:150(anonymous function) @ VM21418:416(anonymous function) @ VM21418:331CompileMetadataResolver.loadNgModuleMetadata @ VM21418:331RuntimeCompiler._loadModules @ VM21415:116RuntimeCompiler._compileModuleAndComponents @ VM21415:86RuntimeCompiler.compileModuleAsync @ VM21415:76PlatformRef_._bootstrapModuleWithZone @ VM21268:328PlatformRef_.bootstrapModule @ VM21268:310(anonymous function) @ main.ts?0e5c:11(anonymous function) @ main.ts?0e5c:11(anonymous function) @ app.js:2883__webpack_require__ @ polyfills.js:53(anonymous function) @ app.js:6055__webpack_require__ @ polyfills.js:53webpackJsonpCallback @ polyfills.js:24(anonymous function)
Uncaught Error: moduleId should be a string in "Ng2SliderComponent".
Jan 8, 2017
I fix this issuue by fixing the ng2-slider.component.js |
Same issue for me |
Same for me. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uncaught Error: moduleId should be a string in "Ng2SliderComponent". See https://goo.gl/wIDDiL for more information. If you're using Webpack you should inline the template and the styles, see https://goo.gl/X2J8zc.componentModuleUrl
The text was updated successfully, but these errors were encountered: