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

@behance/assets-vendor

v3.3.2

Published

Random Collection of Componentry.

Downloads

55

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

chthomaschthomaslanniemiaolanniemiaomtrajano93mtrajano93moskalenmoskalenelewiselewismansinarainmansinarainattamuscattamuscweikinhuangweikinhuangmasemaseagaripianagaripiannemtsovnemtsovbryanpackmanbryanpackmanmatt-oconnellmatt-oconnellmlebrunmlebrunandyroo2000andyroo2000ingluisjimenezingluisjimenezgtuckeradobegtuckeradobetpaparnetpaparnedanicasapitdanicasapitdfoxinatordfoxinatorjelee11jelee11jmedoyjmedoybossjonesbossjonesmtldomtldojusheanjusheanbryanlattenbryanlattensadraeisadraeitracyfogeltracyfogelkangmankangmaniooiiooibenakebenakedavesteindavestein

Keywords

Readme

assets-vendor

3rd party utility libraries here. They must be of sufficient high quality to be included here and offer common functionality.

Cutting a Release

  1. npm version <version number>
  2. git push upstream master --follow-tags
  3. Edit the release notes at https://github.com/behance/assets-vendor/releases

Updating ckeditor

Behance maintains several CKEditor plugins in the behance/ckeditor-dev repo. In order to update to the latest CKEditor, perform the following steps:

  1. clone the behance/ckeditor-dev repo.
  2. merge the latest changes from ckeditor/ckeditor-dev into the behance/ckeditor-dev repo.
  3. from behance/ckeditor-dev, run ./dev/builder/build.sh.
  4. copy ./dev/builder/release/ckeditor/ from behance/ckeditor-dev to the ckeditor dir in this repo.
  5. ensure implementations behave as expected. For the network this includes, at a minimum:
  6. posting a job
  7. adding text to a project from the project editor

Updating FineUploader

Behance maintains our own version of FineUploader in the behance/fine-uploader repo. In order to update to the latest FineUploader, or to generate a new build, perform the following steps:

  1. follow the instructions on http://docs.fineuploader.com/contributing.html
  2. copy the correct files to this repo. As of 5/20/15 that is both the regular fine-uploader.min.js file and the s3.fine-uploader.min.js
  3. Ensure that Behance's custom changes are in place by grepping the code for comments starting with BEHANCE:
  4. Add AMD wrappers around the code to avoid having conflicting globals.

Future modifications to FineUploader should be done as pull requests against the behance/fine-uploader repo.