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

cause-report-configuration

v0.7.0

Published

$ npm install --save cause-report-configuration

Downloads

11

Readme

ReportConfiguration

Installing with npm

$ npm install --save cause-report-configuration

Initialization of the Text-Editor Component

In order to use the Text-editor, make sure to import TextEditorModule in your module and add it to the import list:

imports: [
    ...
    TextEditorModule
  ],

After that, you can call an instance with html.

<app-text-editor 
       #textEditor 
       id="textEditor" 
       [(documentContent)]="selectedTemplate.data" 
       [(placeholders)]="placeholders" 
       (loadDataEvent)="openDialog()" 
       (saveDataEvent)="saveTemplate()">
</app-text-editor> 

The editor component offers various inputs and outputs which can bind to your own components. You can add two-way binding to the data contained within the editor. You can send a list of placeholder options that will be embedded within the editor's menu. You can bind callbacks to decide what to do when the load or save button is pressed.

Customization

To see all available features of CKEditor, please visit the official website: https://ckeditor.com/ckeditor-4/

Customization of the editor's appearance

To change how the editor looks, you need to modify the css file: 'src/assets/document-editor.css'

Customization of the editor's menus

All settings can be tinkered with within the configuration file ('src/app/text-editor/shared/ckeditor-configuration.ts'). If you wish to add custom buttons that don't exist anywhere, please follow the following guide: https://stackoverflow.com/questions/1957156/how-to-add-a-custom-button-to-the-toolbar-that-calls-a-javascript-function

Customization with plugins

The CKEditor community is very active and offers a wide selection of plugins: https://ckeditor.com/cke4/addons/plugins/all These plugins can be downloaded directly and added to the directory: './src/assets/ckeditor/plugins' To include them in the editor's instance, make sure to modify the configuration file ('./src/app/text-editor/shared/ckeditor-configuration.ts') by adding the name of the plugin to the following line: extraPlugins: 'widget,tabletools,imageresizerowandcolumn,NAME_OF_THE_NEW_PLUGIN',.

You can also dynamically load a plugin from an external directory by adding window.CKEDITOR.plugins.addExternal(NAME_OF_THE_NEW_PLUGIN, PATH_TO_YOUR_PLUGIN_DIRECORY); before this.editor = window.CKEDITOR.replace('editor', ckeditorConfiguration); is called in './src/app/text-editor/test-editor.component.ts'.

You can even design your own plugins to interact with the editor. Find more information here: https://ckeditor.com/docs/ckeditor4/latest/guide/plugin_sdk_sample.html When designing your own plugins, it is important to place them in the './src/assets/custom_plugins/' folder to avoid overwriting them when updating the plugins' folder within the ckeditor.