kunagpal / express-boilerplate Goto Github PK

Istanbul is deprecated, and should be replaced with nyc.

Similar in functionality to the Rails and Sails consoles.

Despite the prestart script minifiying static assets, the unused css is still left intact. This can be removed via tools like https://github.com/purifycss/purifycss or https://github.com/giakki/uncss

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

https://github.com/pinojs/pino

Less time spent logging, more time spent serving requests 😄

• Each unit test file uses it's own database, thereby truly isolating it.
• Different categories of tests can be run in parallel instead of series, as is the case now.

Bower has been deprecated and should be swapped out with Webpack, or something similar.

Every model module should export a function that takes in a db argument which prevents having to inject db into global.

Many entries in the scripts section of package.json use direct CLI commands, they should be converted to direct script references.

https://github.com/semantic-release/semantic-release

Similar to #246

Also, e2e test output is not shown in the test sequence, which needs to be fixed.

• Home
• Admin
• Password reset/update
• Sign in/up

• Remove all excessive wrappers around collection helpers.
• This can be done by either exposing collections as model globals, or by resourcing all abstractions from a common Model prototype.

https://github.com/greenkeeper-keeper/meta

Unit test output is completely missing from CI environment logs, leading to the impression that unit tests are never actually run. It is possible that misconfigured CI MongoDB settings are causing this issue. Resolving this will also fix the issue of missing code coverage from the badges section.

Add scripts that tend to the following:

• Creation of a release.
• Creation of a project bundle, that includes the dependencies installed, with included details on the host architecture.
• Deployment scripts (more research needed)
• Creation of a zip archive from the current project state.
• Scripts to generate and publish documentation and the project wiki.

This script should minify css and js files, placing them within a designated folder. The script is intended to run prior to app start, thereby maintaining compressed assets all over.

Introduced by e1a1895 in #321

Due to clustering in the code coverage script, the entire test suite is effectively being run twice, once in the master context, and the second time in the worker context. This needs to be fixed by switching over to Node's child_process instead.

An alternative is to run just the unit tests in the worker context.

https://github.com/jhurliman/node-rate-limiter

• Multi updates default: false
• Multi deletes default: false
• Option to disable RESTful routes for a model altogether default: enabled

The current script replaces bcrypt with bcryptjs in a dumbed down way, this needs to be improved to detect whether or not the target machine can use bcrypt directly.

More research needed here.