npm-build-boilerplate - A collection of packages that build a website using npm scripts.

  •        8

A collection of packages that build a website using npm scripts. autoprefixer, browser-sync, eslint, imagemin-cli, node-sass, onchange, npm-run-all, postcss-cli, svgo, svg-sprite-generator, uglify-js.

https://github.com/damonbauer/npm-build-boilerplate

Tags
Implementation
License
Platform

   




Related Projects

awesome-npm-scripts - Everything awesome related to npm scripts and using npm as a build tool.

  •    Javascript

Everything awesome for using npm as a build tool. You might also like awesome-npm.

nps - :100: All the benefits of npm scripts without the cost of a bloated package

  •    Javascript

Even though npm scripts have a ton of advantages (learn more), it can grow into an unmaintainable mess in your package.json file. Part of the problem is we're configuring scripts in json which has fundamental issues (like no comments).To use nps, it's recommended that you either install it globally (npm i -g nps) or add ./node_modules/bin to your $PATH (be careful that you know what you're doing when doing this, find out how here).

concurrently - Run commands concurrently. Like `npm run watch-js & npm run watch-less` but better.

  •    Javascript

Run multiple commands concurrently. Like npm run watch-js & npm run watch-less but better. I like task automation with npm but the usual way to run multiple commands concurrently is npm run watch-js & npm run watch-css. That's fine but it's hard to keep on track of different outputs. Also if one process fails, others still keep running and you won't even notice the difference.


npm-scripts-example - An example of how to use NPM scripts over Grunt/Gulp & Friends

  •    Javascript

Firstly, you should go and read how to use NPM as a build tool. Then come back here and explore the repository. It's fairly standard, and the bare minimum to show you what a complex config would look like. See some areas for optimising? Great! Send a PR, I'm definitely interested in seeing some great ways to optimise this.

better-npm-run - Better NPM scripts runner

  •    Javascript

The betterScripts script definition can either be a string or sub-object with command and env attributes. Values defined in the env block will override previously set environment variables. Note that depending on the OS and terminal you're using, dots, spaces or other special characters in the command path may be treated as separators and the command will be parsed wrong.

grunt-ts - A grunt task to manage your complete typescript development to production workflow

  •    Javascript

Grunt-ts is an npm package that handles TypeScript compilation work in GruntJS build scripts. It provides a Grunt-compatible wrapper for the tsc command-line compiler, and provides some additional functionality that improves the TypeScript development workflow. Grunt-ts supports compiling against tsconfig.json or even a Visual Studio project directly. Grunt-ts is itself written in TypeScript. Do you use grunt-ts? Would you like to help keep it up-to-date for new TypeScript versions? Please let @nycdotnet know.

collide

  •    Javascript

- `npm install`- `npm install -g browserify`- `npm run test` runs jasmine-node tests. `npm run autotest` will watch and test- `npm run build`- Generated file `dist/collide.js` is require/CommonJS/window friendly. If you include it, it will be included as `window.collide`.- Note: the `collide.js` found in project root is only updated on release. The built version in dist is not added to git and should be used while developing.

windows-build-tools - :package: Install C++ Build Tools for Windows using npm

  •    TypeScript

After installation, npm will automatically execute this module, which downloads and installs Visual C++ Build Tools, provided free of charge by Microsoft. These tools are required to compile popular native modules. If not already installed, it will also install Python 2.7, configuring your machine and npm appropriately. Both installations are conflict-free, meaning that they do not mess with existing installations of Visual Studio, C++ Build Tools, or Python. If you see anything that indicates otherwise, please file a bug.

npx - execute npm package binaries

  •    Javascript

npx [options] <command>[@version] [command-arg]... npx [options] [-p|--package <pkg>]... <command> [command-arg]...

npm-windows-upgrade - :rocket: Upgrade npm on Windows

  •    Javascript

Upgrading npm on Windows requires manual steps to ensure that PowerShell/CMD find the new version of npm. This is a small tool made with ❤️ for npm and Node, reducing the process to a simple command. First, ensure that you can execute scripts on your system by running the following command from an elevated PowerShell. To run PowerShell as Administrator, click Start, search for PowerShell, right-click PowerShell and select Run as Administrator.

scripty - Because no one should be shell-scripting inside a JSON file.

  •    Javascript

Indeed, this is much simpler, but it can quickly become a mess. Take a look at what happened to our testdouble.js library's package.json. Using npm-scripts for everything is simple to start with, but it can't hope to guard against the complexity that naturally accumulates over the life of a project. From this point on, you can run npm run foo:bar and scripty will use npm's built-in npm_lifecycle_event environment variable to look up scripts/foo/bar and execute it for you.

megaboilerplate - Handcrafted starter projects, optimized for simplicity and ease of use.

  •    CSS

Mega Boilerplate is a starter project generator that focuses on simplicity and ease of use, while providing you with flexibility of choices. It was heavily inspired by the Hackathon Starter, but unlike it, you can customize any part of your application stack — from web framework and database to CSS preprocessor and client-side JavaScript framework. Currently, generators are primarily limited to Node.js web apps, but I am planning to expand support for other platforms and languages in the near future.Note: If you have selected Gulp or NPM build tool, you may also need to run npm run build command.

create-next-app - Create Next.js apps in one command

  •    Javascript

Open http://localhost:3000 to view your running app. When you're ready for production, run npm run build then npm run start. You don't need to install or setup Webpack or Babel. They come packaged with next, so you can just start coding.

codebox-npm - Serverless private npm registry using https://serverless.com/

  •    Javascript

Codebox npm is a serverless npm registry to allow companies that wish to keep their intellectual property. It allows sharing of npm modules within a company but additionally allows access to all of the modules on public npm. One other major difference is that it replaces npm login authentication to be via github / github enterprise. Users are always required to be authenticated when using codebox as their npm registry. It is currently compatible with the latest version of the npm & yarn cli.

forrest - An npm scripts desktop client

  •    Vue

Forrest is an npm desktop client to deal with daily work flows. It lets you control common npm commands and all custom scripts defined in the package.json. Individuals making significant and valuable contributions are given commit-access to the project to contribute as they see fit. This project is more like an open wiki than a standard guarded open source project.

node-fibers - Fiber/coroutine support for v8 and node.

  •    C++

Fibers, sometimes called coroutines, are a powerful tool which expose an API to jump between multiple call stacks from within a single thread. This can be useful to make code written for a synchronous library play nicely in an asynchronous environment. Note: node-fibers uses node-gyp for building. To manually invoke the build process, you can use node-gyp rebuild. This will put the compiled extension in build/Release/fibers.node. However, when you do require('fibers'), it will expect the module to be in, for example, bin/linux-x64-v8-3.11/fibers.node. You can manually put the module here every time you build, or you can use the included build script. Either npm install or node build -f will do this for you. If you are going to be hacking on node-fibers, it may be worthwhile to first do node-gyp configure and then for subsequent rebuilds you can just do node-gyp build which will be faster than a full npm install or node-gyp rebuild.