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

svn-resolver

v0.2.5

Published

SVN pluggable resolver for Bower, overriding and enhancing the default functionality

Downloads

4

Readme

svn-resolver

SVN pluggable resolver for Bower. Bower has some support for SVN, but this resolver overrides the default to provide enhanced functionality to better support typical SVN workflows. So far it allows storage of credentials in .bowerrc, provides the capability to update from trunk, and allows SVN targets which do not use the typically trunk/tags structure.

NPM

Install

Either install globally with npm:

npm install --global svn-resolver

or add as a local dependency in your package.json.

Usage

Add the following to .bowerrc:

{
  "resolvers": [
    "svn-resolver"
  ],
  "svnResolver": {
    "username": "[USERNAME]",
    "password": "[PASSWORD]"
  }
}

Credentials are optional, if not provided it will use the credentials saved by SVN (if any). There are clearly security considerations with storing credentials in plain text within .bowerrc, but it may be helpful to simplify a build process.

Now in bower.json we can use dependencies of the form:

"dependencies": {
  "MyPrivateDependency": "svn+https://svn.example.com/my-private-dependency#",
}

Typically the target directory in SVN will need to use the conventional trunk/branches/tags directory structure. Versions are mapped as follows:

  • # for the latest revision from trunk (bower update works)
  • #trunk for the trunk, but bower update will not pull down new revisions. This probably has little use but is provided to match the default Bower behaviour.
  • #[tag] for tags/[tag] (bower update will not work but since tags should not change, this should not be an issue)
  • #[revision].0.0 or #r[revision] will use trunk at the specified [revision].

Alternatively, it is possible to use a target directory that does not use the trunk/branches/tags structure by appending -no-trunk to the version:

  • #-no-trunk for the latest revision
  • #r[revision]-no-trunk for a specific revision