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

angular-render-html-once

v1.2.0

Published

Angular helper component for HTML string that should be rendered once and maintaned later

Downloads

3

Readme

angular-render-html-once

This library helps to keep HTML string rendered once, even if they originally were rendered server-side.

Whenever rendering would occur, and HTML string has already been rendered, resulting DOM elements will be re-used.

This is quite important when integrating angular app with external code maintained by some other library.

Usage

enabing/disabling

One-time rendering is enabled by default. If you wish to disable it permanently, use RenderHtmlOnceComponent.disable() static method - it will prevent from caching/using cache from now on. Complementary static method RenderHtmlOnce.enable() will enable it again.

bootstrap (optional)

Call no-argument static method RenderHtmlOnceComponent.registerServerSideRenderedComponents() wherever applicable (eg. in your application module's constructor) to have it scan for any server-side rendered components that could be already used.

Important: this needs to be done before any angular rendering occurs, since first thing angular does is clearing any existing content of root DOM element.

Component

  • use <render-html-once> component wherever you would normally use [innerHtml] directive
  • inputs:
    • id required - plain old HTML id attribute; required to match components whenever they could be destroyed and created again (or created from scratch browser-side and match them with their server-side rendered counterparts)
    • htmlContent required - HTML content string you wish to have embedded within component
    • cacheable (optional; default: true) - allows enabling/disabling caching of specific <render-html-once> instance; turning it off in runtime also clears instance-related cache

Requirements

  • angular ^8.0.0