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

generator-force

v1.0.7

Published

Generator for force.com platform.

Downloads

27

Readme

generator-force NPM version Build Status Dependency Status Coverage Status

Installation

First, install Yeoman and generator-force using npm (we assume you have pre-installed node.js).

npm install -g yo
npm install -g generator-force

Now clone your project or make a new folder and cd to it. Next setup your project

yo force

This will ask a few questions to set up your user and org for retrieve and deploy

  • project name (defaults to folder name)
  • sandbox (defaults to false)
  • username (username for your dev org)
  • password (password + secToken)
  • repo (optional setup for package.json github)

That's it your done

You have just setup your project with yo force. Now lets look at the commands you have.

yo force:retrieve 'optional package name'

NOTE: With out the package name yo force will assume you have a src/package.xml file and will retrieve based on it's contents.

yo force:deploy

New salesforce-lightning-cli added by default /src/aura.

Now each project gets setup with the custom rules from the cli tool and will run a default lint before deploy. But you can run a lint manually also. This will scan src/aura/**/*.js files

npm run lint

S.P.A. Setup

Now lets create a new spa and generate your new project/spa/spaName:

yo force:ng 'spaName'

This will create a folder inside of the spa folder with the name of your spa, cd and npm install your dependencies

Now your Project folder structure should look like this (if you named the spa spaName)

project
│   README.md
│   package.xml    
│   src (sfdc: class, page, trigger)
└───spa
    │
    └───spaName
    │   package.json
    │   webpack.config.js
    │   ...

Now get to work!

npm start

To push your spa / static resource use

npm run deploy

This will push a non minified version of your spa and meta to the org.

npm run production

This will push a minified version of your spa and meta to the org.

Getting To Know Yeoman

Yeoman has a heart of gold. He's a person with feelings and opinions, but he's very easy to work with. If you think he's too opinionated, he can be easily convinced. Feel free to learn more about him.

License

MIT © Matt Newell