Skip to content
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

Using angular2-markdown insinde node_modules folder #68

Closed
cleptomaniac361 opened this issue Jul 14, 2017 · 2 comments
Closed

Using angular2-markdown insinde node_modules folder #68

cleptomaniac361 opened this issue Jul 14, 2017 · 2 comments

Comments

@cleptomaniac361
Copy link

I want to use the markdown module inside my node_modules folder to parse some README.md files in some reusable components inside an external module. I tried to import the MarkdownModule with import {MarkdownModule} from "angular2-markdown"; inside my external.module.ts file in the node_modules folder. I also added the MarkdownModule.forRoot() to my imports inside the @NgModule decorator. When I use <markdown> ##Example## </markdown> inside an HTML file in my module, i receive the following error:

Unhandled Promise rejection: Template parse errors:
'markdown' is not a known element:
1. If 'markdown' is an Angular component, then verify that it is part of this module.
2. If 'markdown' is a Web Component then add "CUSTOM_ELEMENTS_SCHEMA" to the '@NgModule.schemas' of this component to suppress this message.

Pointing to my Tag

Is it possible to use the markdown module inside the node_modules folder or do I have to find another way to parse my README.md files?

@dimpu
Copy link
Owner

dimpu commented Aug 14, 2017

@cleptomaniac361 Mode does not register properly.

@dimpu dimpu closed this as completed Oct 20, 2017
@Axure
Copy link

Axure commented Nov 25, 2017

In my case, I mis-imported the component into the "routing module", instead of the module. Hope this helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants