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

cc

v3.0.1

Published

Code style linter for C++ source files used in Node.js native addons

Downloads

2,154

Readme

cc

Code style linter for C++ source files used in Node.js native addons.

Follows the Google C++ Style Guide.

As standard, semistandard and xo are to your JavaScript source files, cc is to your C++ source files.

Using from the command line

npx cc

Adding to a native module as a development dependency

npm install cc --save-dev

Add cpplint to the test script of your project's package.json file.

The following example uses xo for linting JavaScript, cpplint for linting C++ and ava for unit tests.

{
  "name": "awesome-native-package",
  "scripts": {
    "test": "xo && cpplint && ava"
  },
  "devDependencies": {
    "ava": "^2.4.0",
    "cc": "^3.0.0",
    "xo": "^0.25.3"
  }
}

Defaults

"cc": {
  "linelength": "80",
  "files": [
    "**/*.cc",
    "**/*.h"
  ],
  "ignore": [
    "node_modules/**",
    "vendor/**"
  ],
  "filter": []
}

Files listed in .gitignore or contained within any "dot" directories (e.g. .git) are also ignored.

Example

Allow a line length of 120 characters and ignore all include checks:

{
  "name": "awesome-native-package",
  "scripts": {
    "test": "cpplint"
  },
  "devDependencies": {
    "cc": "^3.0.0"
  },
  "cc": {
    "linelength": "120",
    "filter": [
      "build/include"
    ]
  }
}

Thanks

Licence

Copyright 2017, 2019, 2020 Lovell Fuller.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.