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

atlassian-wrm

v1.12.0

Published

Enables AMD modules in Atlassian Plugin.

Downloads

76

Readme

Enables AMD modules in Atlassian Plugin.

How it works - it needed to be run during Atlassian Plugin compilation. It analyses AMD modules in the Plugin and stores this analysis in target/classes/atlassian-modules.xml. At runtime Web Resource Manager uses this metadata to serve AMD modules to the Browser.

Command-line usage

Install it as global NPM module, you need to have Node.JS and NPM.

npm install -g atlassian-wrm

Go to your plugin and compile AMD modules

cd <your-atlassian-plugin>
wrm-compile

Usage with node.js build tools

var compile = require('atlassian-wrm').compile;

compile(atlassianPluginXmlPath, outputDir, function (err) {
    if (err) {
        return console.error(err);
    }
    console.info("AMD modules for \"" + atlassianPluginXmlPath + "\" successfully compiled.");
});

Please provide feedback

Currently it's unclear how we should integrate this tool in Front-End workflow to optimise development experience.

  • Hardcode it in AMPS and run it as a step during maven build?
  • Distribute it as a minimal npm library and allow Front-End devs to integrate it into their own custom build workflow, in tools like gulp or grunt?
  • How we should handle ES6? Should it be hardcoded and supported out of the box or we should give front-end devs freedom to choose their own build tools and languages like ES6, TypeScript or CoffeeScript and aim for this library being easily integrated in those workflow?
  • What other use cases do we need to support?

Also, feel free to hack this script and submit PRs.

TODO

  • It uses a little unusual approach to handle async stuff, maybe it would be better to rewrite it with some classical async helper like https://github.com/kriskowal/q but, it could be done later.
  • Allow to specify prefix for AMD modules to search in src or target folders.
  • Adapters for grunt, gulp etc.