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

grunt-build-atom-shell

v2.1.1

Published

Grunt task to build atom-shell and rebuild node modules

Downloads

17

Readme

grunt-build-atom-shell

Build atom-shell from Git, and rebuild native modules. This is a mostly drop-in replacement for grunt-download-atom-shell, in that, you can replace your use of it with this package at the same point in the Atom build process and everything should Just Work.

Why even would I do this?

The main reason to do this is because of atom/atom-shell#713 - trying to rename Atom after-the-fact isn't possible on Windows without some serious rigging. This package fixes that issue, as well as allows you to use arbitrary builds of Atom Shell (i.e. no more waiting for a new release for a bugfix).

Installation

Install npm package, next to your project's Gruntfile.js file:

npm install --save-dev grunt-build-atom-shell

Add this line to your project's Gruntfile.js:

grunt.loadNpmTasks('grunt-build-atom-shell');

Options

  • buildDir - Required Where to put the downloaded atom-shell
  • tag - Required A tag, branch, or commit of Atom Shell to build
  • projectName - Required A short name for your project (originally 'atom')
  • productName - Required The name of the final binary generated (originally 'Atom')
  • targetDir - Where to put the resulting atom-shell, defaults to ./atom-shell
  • config - Either 'Debug' or 'Release', defaults to 'Release'
  • remoteUrl - The Git remote url to download from, defaults to official Atom Shell
  • nodeVersion - The version of Node.js to use; see the section below for how to configure this

Example

Gruntfile.js

module.exports = function(grunt) {
  grunt.initConfig({
    'build-atom-shell': {
      tag: 'v0.19.5',
      nodeVersion: '0.18.0',
      buildDir: (path.env.TMPDIR || path.env.TEMP || '/tmp') + '/atom-shell',
      projectName: 'mycoolapp',
      productName: 'MyCoolApp'
    }
  });
};

Correctly setting nodeVersion

Different versions of Atom Shell expect to be linked against different versions of node.js. Since grunt-build-atom-shell allows you to use arbitrary commits of Atom Shell, there is no way for it to know which version is correct to use, so it must be explicitly provided. If you don't explicitly provide a version, we will guess the latest version, which may or may not be correct.

  • 0.19.x series - 0.18.0
  • 0.20.x series - 0.20.0
  • 0.21.x series - 0.21.0
  • 0.22.x series - 0.22.0

These numbers don't match the official node.js versions, because they also reflect patches that Atom puts into node.js to make it compatible with Chromium.