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

@pageboard/html

v0.12.35

Published

Elements can be defined in three parts:

Downloads

398

Readme

pageboard-elements

Elements can be defined in three parts:

  • view, needed by pageboard-read to render blocks
  • schema, needed by pageboard-write to edit attributes, and by pageboard-api to validate blocks
  • edit, defines the specs of the rich text content and optionally a render function for edition.

It's up to pageboard-read and pageboard-write main files to load the files, using either js files or html imports.

everything in a single, requireable js file

Exports everything in a single file, accessible from public/elements/myname.js

(function(exports) {
	exports.myname = {
		view: function(doc, block) {
			// do more than that of course
			return doc.createElement('div');
		},
		edit: function(doc, block) {
			// optional function
		},
		properties: {
			myprop: {
				type: 'string'
			}
		}
		specs: {
			mycontent: 'block+'
		}
	};
})(typeof exports != "undefined" ? exports : window.Pagecut.modules);

multiple js files

Exports edit, view, schema from different files, accessible from public/elements/myname/view.js public/elements/myname/edit.js public/elements/myname/index.js (defines the schema, must be requireable)

It is advised to test before assigning like this

(function(exports) {
	if (!exports.myname) exports.myname = {}; // test here
	exports.myname.properties = {
		myprop: {
			type: 'string'
		}
	};
})(typeof exports != "undefined" ? exports : window.Pagecut.modules);

view and edit files are not supposed to be requireable

(function(exports) {
	if (!exports.myname) exports.myname = {}; // test here
	exports.myname.view = function() {};//...
})(window.Pagecut.modules);

multiple html imports

This layout is also supported: public/elements/myname/view.html public/elements/myname/edit.html public/elements/myname/index.js (defines the schema, must be requireable)

Where view and edit load their assets as script (inline or not), link, or style tags.