npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@ngx-markdown/core

v0.2.2

Published

Angular 2+ markdown to html using marked a markdown parser and compiler.

Downloads

79

Readme

@ngx-markdown/core

Angular 2+ markdown to html module using marked a markdown parser and compiler.



Demonstration

Get simple example demonstration usage from github repository by opening your command line and do the following:

git clone https://github.com/ngx-markdown/demo.git
cd demo
npm install && npm start

Open http://localhost:4200/ in your browser.

Installation

To install, run:

npm install --save @ngx-markdown/core

Usage

  1. In file ./example.module.ts
// external
import { NgModule } from '@angular/core';
import { CommonModule } from '@angular/common';

// @ngx
import { MarkdownModule } from '@ngx-markdown/core';

// internal 
import { ExampleComponent } from './example.component';

@NgModule({
  imports: [
    // external
    CommonModule,

    // internal
    MarkdownModule.forRoot({
      // this options are defaults when use forChild().
      options: {
        gfm: true,
        tables: true,
        breaks: true,
        pedantic: false,
        sanitize: false,
        smartLists: true,
        smartypants: false
      },
      // template while loading
      loadingTemplate: `<div> Loading ... </div>`
    })    
  ],
  declarations: [ ]
})
export class ExampleModule { }
  1. In file ./example.component.ts
// external
import { Component, OnInit } from '@angular/core';

// internal

@Component({
  selector: 'example-component',
  templateUrl: './example.component.html'
})
export class ExampleComponent implements OnInit {
  stringToTransform = `**my bold**
  [link](http://example.com)
  {{language}}
  `;
  options = {
    gfm: true,
    tables: false, // changed
    breaks: true,
    pedantic: false,
    sanitize: false,
    smartLists: true,
    smartypants: false
  };
  interpolate = {
    language: 'I speak english'
  };
  callback = (error: any, result: string) => {
    console.log(`callback`, error, result);
  };
  getResult(event) {
    console.log(`result,`, event);
  }
  constructor() { }

  ngOnInit() { }
}
  1. In file ./example.component.html
<!-- Directive: ng-content -->
<div ngx-markdown [interpolation]="interpolate" [options]="options" [callback]="callback">
  **my bold** {{language}}
</div>

<!-- Component: ng-content -->
<ngx-markdown [interpolation]="interpolate" [options]="options" [callback]="callback">
  **my bold**
  [link](http://example.com)
  {{language}}
</ngx-markdown>

<!-- Component: dynamic with property `string` -->
<ngx-markdown
  [interpolation]="interpolate"
  [options]="options"
  [callback]="callback"
  [string]="stringToTransform"
  (result)="getResult($event)"></ngx-markdown>

<!-- Directive: dynamic with property `ngxmarkdown` -->
<div
  [ngxmarkdown]="stringToTransform"
  [callback]="callback"
  [interpolation]="interpolate"
  [options]="options"
></div>

Attributes

| Name | Type | Description | |----------|----------------|---------------------------| | callback | ((error: any, parseResult: string) => void) | undefined | Function called when the string or ngxmarkdown has been fully parsed. | | interpolation | Object | undefined | Data property values to inject. | | ngxmarkdown (directive) | string | "String of markdown source to be compiled." | | options | marked.MarkedOptions | undefined | Marked options how to compile markdown string. | | string (component) | string | "String of markdown source to be compiled." |

Events

| Name | Type | Description | |----------|----------------|---------------------------| | result | string | It returns fully parsed markdown string. |

Lifecycle Hooks

Angular Lifecycle Hooks

When property change is set, its setter calls markdownToHtml() method to compile markdown string.

ngAfterViewInit(): When input property string is undefined, store ng-content and set property change to true.

ngDoCheck(): Detect input property options changes with KeyValueDiffers, and set property change to true if detected.

ngOnChanges(): Detect input property callback and string changes, and set property change to true if detected.

Style guide

Angular style guide

GIT

Commit

Versioning

Semantic Versioning 2.0.0 http://semver.org/

Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

FAQ
How should I deal with revisions in the 0.y.z initial development phase?

The simplest thing to do is start your initial development release at 0.1.0 and then increment the minor version for each subsequent release.

How do I know when to release 1.0.0?

If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backwards compatibility, you should probably already be 1.0.0.

License

MIT © ngx-markdown

Donate

Click to donate