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

juicy-ace-editor-es6

v3.0.0

Published

Custom Element wrapper for Ace code editor

Downloads

2

Readme

<juicy-ace-editor>

Even more embeddable code editor. Custom Element - just one tag, and no JS needed to provide Ace - The High Performance Code Editor

ES6 Modules version

This version was created using the ES6-modules branch of the original juicy-ace-editor repo. A Github Actions workflow was balking at using the original repo, so I merged it into my fork's master.

The rest of these instructions are very outdated.

Demo

Check it live!

Play & Configure with kitchen sink

Features

Besides Ace features, <juicy-ace-editor> does:

  • provide extremely clean and easy way to embed it (see Usage)
  • observe DOM changes:
  • Update your code by just updating Element's text content
  • Change Editor's setting by changing DOM attributes
  • Compatible with Shadow DOM v0 and v1
  • Custom Elements v1 (more)

You can still fiddle with Ace editor programmatically using <juicy-ace-editor>.editor.

Install

Install the component using Bower:

$ bower install juicy-ace-editor --save

Or download as ZIP.

Usage

  1. Import Web Components' polyfill (if needed):

    <script src="bower_components/webcomponentsjs/webcomponents-lite.js"></script>
  2. Import Custom Element:

    <link rel="import" href="bower_components/juicy-ace-editor/juicy-ace-editor.html">
  3. Start using it!

<juicy-ace-editor theme="ace/theme/monokai">Type your code here...</juicy-ace-editor>

Attributes

Attribute | Options | Default | Description --- | --- | --- | --- theme | String | | Editor#setTheme at Ace API mode | String | | EditSession#setMode at Ace API fontsize | String | | Editor#setFontSize at Ace API softtabs | Boolean | | EditSession#setUseSoftTabs() at Ace API tabsize | Boolean | | Session#setTabSize() at Ace API readonly | Boolean | | Editor#setReadOnly() at Ace API wrapmode | Boolean | | Session#setWrapMode() at Ace API shadow-style | String | | CSS selector for a <style> element, from the same (shadow)tree, to be injected to shadow root when stamped or attributeChanged

Properties

Name | Description --- | --- editor | Ace editor object. value | editor.get-/setValue()

Events

Name | Description --- | --- change | Triggered when editor content gets changed editor-ready | Triggered once Ace editor instance is created.

Web Components v0 vs v1

Currently, this element supports both Shadow DOM v1 and v0, but only Custom Elements v1. If your environment uses Custom Elements v0 only, we strongly recommend to use lightweight v0 to v1 polyfill

bower install --save document-register-element

Who uses it?

Contributing and Development

History

For detailed changelog, check Releases.

License

MIT