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

aem-bookmarklets

v0.2.3

Published

A set of useful bookmarklets that you can you to slightly speed up development on the AEM

Downloads

17

Readme

http://panda-soft.io

Build Status Coverage Status dependencies Status devDependencies Status JavaScript Style Guide

AEM Bookmarklets

A set of useful bookamarklets for your browser that can be used with AEM based projects.

Bookmarklets

Author ↔ Publish Toggle

Switching between author and publish can be quite frustrating. You need to remove /editor.html... change domain... etc... wow... doing that 50 times a day can be very annoying.

Add this bookmarklet and whenever you will be on a given page in author mode or on publish is will toggle you between them.

Note, that it works in both /sites.html view and ./editor.html.

WCMMode Disabled Toggle

If you wish to quickly preview the content and then get back to the view you may use this little snippet.

Usage

Some of the bookmarklets will just work OOTB. Others, like Author <-> Publish Toggle require some additional configuration.

~~In order to generate bookmarklets you just need to run aem-bookmarklets <pathToConfig>.~~

For the time being the only way to generate the bookmarklet is to checkout the repository add configuration file and run npm run build -- ./my-config-file.js. With next version I will try to wrap the code into an easier to use CLI command.

Configuration

Configuration is pretty simple, all you need to do is create an empty *.js file.

Example:

module.exports = {
    aemEnvironmentMapping: {
        // author instance url                         // publish instance url
        'localhost:4502/content/we-retail/us/en.html': 'localhost:4503/content/we-retail/us/en',
        'author.dev.example.com/content/example-portals/example-portal-pl': 'pl.dev.example.com',
        'author.dev.example.com/content/example-portals/example-portal-europe/en': 'europe.dev.example.com/en',
        'author.dev.example.com/content/example-portals/example-portal-europe/fr': 'europe.dev.example.com/fr',
        'author.dev.example.com/content/example-portals/example-portal-europe/de': 'europe.dev.example.com/de',
    },
    publishViewExtension: '.html' // this item is relevant when we are clicking from /sites.html on the WCMModeToogle bookmarklet 
};

We need to provide this configuration as usually the paths on dispatcher are way shorter then the ones on author instance. Thus we need this mapping between URL to author content and the URL to publish

Development

  1. npm install
  2. npm test
  3. npm run build -- <config> - in case config is not provided it will fallback to config.js