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

mavenlink-js

v1.2.1

Published

This repository encapsulates shared assets and the Mavenlink Backbone Models and Collections used to interact with the Mavenlink API.

Downloads

25

Readme

Mavenlink JS

This repository encapsulates shared assets and the Mavenlink Backbone Models and Collections used to interact with the Mavenlink API.

Styleguide Installation

Add this line to your application's Gemfile:

gem 'mavenlink-js'

The models will then be available via the Rails asset pipeline.

Bootstrap the following on the global JavaScript namespace:

window.Mavenlink.svgImagePath = 'path/to/compiled/svg';

API Installation

Add dependency to your application's package.json

"dependencies": {
    ...
    "mavenlink-js": "[email protected]:mavenlink/mavenlink-js.git#[SHA]",
    ...
}

Run yarn install

Development

Important: After you merge your branch into master

On bigmaven, update the mavenlink-js dependency in package.json to point back to master. Then run yarn upgrade mavenlink-js which will update yarn.lock (equivalent to Gemfile.lock) to have the new sha.

Be sure to check in yarn.lock so that CI/deploy will grab the right artifacts!

Running Specs

To run the specs on the command line, run:

yarn test

Adding an endpoint (Model + Collection)

  1. Add Model with correct brainstem_key and url properties in src/models
  2. Add index entry for Model in src/models/index.coffee (in alphabetical order)
  3. Add Collection with correct url and model properties in src/collections
  4. Add index entry for Collection in src/collections/index.coffee (in alphabetical order)
  5. Add the collection the storage manager in src/base.coffee (in alphabetical order)
  6. Add to the builders in src/helpers/builders.coffee in order generate models for testing purposes
  7. Add specs for Model and Collection in spec/models/model-name-spec.coffee

For an example, see https://github.com/mavenlink/mavenlink-js/pull/301

Develop your application against a local checkout of mavenlink-js

In mavenlink-js, run: yarn unlink; yarn install; yarn link

In your application, run: yarn link mavenlink-js

Restart webpack and karma

When you are done, run: yarn unlink mavenlink-js and then yarn install to grab the original mljs package again

Restart webpack and karma

Develop/Update your application against a remote checkout of mavenlink-js

First, make sure you've unlinked mavenlink-js in the application and ensure you are updated with yarn install

In your application, change package.json to point to proper feature branch in dependencies i.e.

"mavenlink-js": "[email protected]:mavenlink/mavenlink-js.git#your-branch-or-SHA"

Run yarn upgrade mavenlink-js