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

@rickkas7/particle-builder

v0.0.4

Published

Tool for building Particle projects, typically from Travis

Downloads

4

Readme

particle-builder-RK

Tool to automatic builds of particle projects, typically used from Travis, but can also be used locally.

Running manually

Install dependencies:

npm install

Create a build.yml file in the target directory. This is typically the top level library or project directory that contains a library.properties file or the project.properties file.

Here's a simple build.yml:

- build: examples/1-simple-SpiffsParticleRK
  photon: [0.7.0]
  p1: [latest]

This builds the example 1 for the Photon (system firmware 0.7.0) and the p1 (latest release version).

Or, a more complicated example:

- build: examples/1-simple-SpiffsParticleRK
  photon: [0.6.3, 0.7.0, 0.8.0-rc.8]
  p1: [0.7.0]
  electron:  [0.6.3, 0.7.0, 0.8.0-rc.8]
- build: examples/2-self-test-SpiffsParticleRK
  photon: [0.7.0]

Unlike the default in Travis, this does not default to creating an n x n matrix, as in most cases this just results in a very large number of unnecessary builds. For example, the differences between the Photon and P1 are minimal, so the test coverage of the P1 is reduced in the example above.

Run the build, specifying the path to the source directory you want to build:

npm start /Users/rick/Documents/src/SpiffsParticleRK

Running from Travis

The overhead of setting up particle-builder is pretty high because it needs to install the particle-cli package. Instead of doing one platform and one version from each VM spawned by Travis, it runs a bunch of Particle builds from a single Travis VM. This makes sense because the Particle builds are small, and are run from the Particle cloud compiler, anyway, so there are no build artifacts to worry about.

Thus you'll end up having two yml files, one for the Particle build (build.yml) and one for Travis.