tomoat / koa2-generator Goto Github PK

License: MIT License

JavaScript 90.48% CSS 0.41% Less 0.41% Sass 0.37% SCSS 0.50% Stylus 0.37% EJS 1.12% Handlebars 1.06% Pug 1.98% Nunjucks 1.67% Twig 1.63%

koa koa2 koajs koa2-generator generator

koa2-generator's Introduction

koa-generator

Koa' application generator.

Installation

$ npm install -g koa2-generator

Quick Start

The quickest way to get started with koa2 is to utilize the executable koa2(1) to generate an application as shown below:

Create the app:

if you use hogan template engine

$ koa2 --view hogan ./app && cd ./app

if you want use yarn manage your application modules

$ npm i -g yarn

Install dependencies:

$ npm install
or
$ yarn install

Start your Koa app at http://localhost:3000/:

$ npm start
or 
$ yarn start

Command Line Options

This generator can also be further configured with the following command line flags.

Usage: koa2 [options] [dir]

options:

-h, --help          output usage information
-v, --version       output the version number
-e, --ejs           add ejs engine support
    --hbs           add handlebars engine support
    --pug           add pug engine support
    --hjs           add hogan.js engine support
    --njk           add nunjucks engine support
    --view <engine> add view <engine> support (ejs|hbs|hogan|jade|pug|twig|vash) (defaults to jade)
-c, --css <engine>  add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
    --git           add .gitignore
-f, --force         force on non-empty directory

License

MIT

koa2-generator's People

Contributors

Stargazers

Watchers

Forkers

189

koa2-generator's Issues

An in-range update of supertest is breaking the build 🚨

The devDependency supertest was updated from `3.3.0` to `3.4.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

supertest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ ci/circleci: Your tests are queued behind your running builds (Details).
❌ semaphoreci: The build failed on Semaphore. (Details).
❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v3.4.0

PR-532 - Packages updated, pipeline more explicit, documentation updated (thanks @rimiti)
PR-517 - Documentation updated (thanks @oprogramador)
PR-513 - Use more robust Array instance check (thanks @rubendg)

Commits

The new version differs by 14 commits.

5640ac9 3.4.0
60f8a9e Merge pull request #532 from visionmedia/v3.4.0
43bfae1 doc(History.md) changelog updated
fc1568d doc(README.md) cookie example added
3192d96 chore(package-lock.json) file updated
b3d271f chore(package.json) blocks reorganized, nock removed
aeae0f3 chore(.travis.yml) pipeline more explicit
53feddc chore(test/supertest.js) obscure test removed
50c59d6 Merge pull request #519 from oprogramador/patch-3
6ca3897 Merge pull request #517 from oprogramador/patch-2
0146d81 auth info in README
d853b37 fix typo in README
8158979 Merge pull request #513 from rubendg/use-isarray
550613b Use more robust Array instance check

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Middlewares Support

Middlewares

An in-range update of babel-eslint is breaking the build 🚨

Version 7.2.3 of babel-eslint just got published.

Branch	Build failing 🚨
Dependency	babel-eslint
Current Version	7.2.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As babel-eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

- ✅ **semaphoreci** The build passed on Semaphore. [Details](https://semaphoreci.com/tomato/koa2-generator/branches/greenkeeper-babel-eslint-7-2-3/builds/1),- ✅ **ci/circleci** Your tests passed on CircleCI! [Details](https://circleci.com/gh/tomoat/koa2-generator/8?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link),- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/tomoat/koa2-generator/builds/224521185)

Commits

The new version differs by 2 commits0.

94bb5a1 7.2.3
dfaff04 Fix flow type spread handling (#465)

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of bluebird is breaking the build 🚨

The devDependency bluebird was updated from `3.5.2` to `3.5.3`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

bluebird is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ semaphoreci: The build failed on Semaphore. (Details).
❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
❌ ci/circleci: Your tests failed on CircleCI (Details).

Release Notes for v3.5.3

Bugfixes:

Update acorn dependency

Commits

The new version differs by 7 commits.

a5a5b57 Release v3.5.3
c8a7714 update packagelock
8a765fd Update getting-started.md (#1561)
f541801 deps: update acorn and add acorn-walk (#1560)
247e512 Update promise.each.md (#1555)
e2756e5 fixed browser cdn links (#1554)
7cfa9f7 Changed expected behaviour when promisifying (#1545)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

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.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

engines was only updated if it defined a single version, not a range.
.nvmrc was updated to Node.js 10
.travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of babel-eslint is breaking the build 🚨

Version 7.2.0 of babel-eslint just got published.

Branch	Build failing 🚨
Dependency	babel-eslint
Current Version	7.1.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

v7.2.0

New Feature

Add option to disable code frame. (#446) (Luís Couto)

Main change is just an option to disable the codeframe (added in v7.1.1) for html output and more (thanks to @Couto).

{
  "parser": "babel-eslint",
  "parserOptions": {
    "codeFrame": false
  },
  "extends": "eslint:recommended"
}

Bug Fix

[flow] Process polymorphic type bounds on functions (#444) (Alex Rattray)

Internal/Docs

Use lodash instead of lodash.pickby. (#435) (wtgtybhertgeghgtwtg)
Updates ESLint version/remove unnecessary config (Kai Cataldo)
Remove broken ESLint tests (Kai Cataldo)
Upgrade outdated dependencies (Kai Cataldo)
remove deprecated rule examples [skip ci] (Henry Zhu)
update readme [skip ci] (Henry Zhu)
chore(package): update eslint-config-babel to version 6.0.0 (#433) (Henry Zhu)
Update to use Node 4 features (#425) (Nazim Hajidin)
chore(package): update eslint-config-babel to version 4.0.0 (#430) (greenkeeper[bot])
add badges [skip ci] (Henry Zhu)
Revert "use *" (#426) (Henry Zhu)
use * (#421) (Henry Zhu)
chore(package): update eslint-config-babel to version 3.0.0 (#423) (greenkeeper[bot])

Commits

The new version differs by 17 commits .

4db4db5 7.2.0
4499412 Use lodash instead of lodash.pickby. (#435)
a2c3b30 [flow] Process polymorphic type bounds on functions (#444)
515adef Add option to disable code frame. (#446)
ce66e73 Merge pull request #447 from kaicataldo/clean-up-eslint
b49ab20 Updates ESLint version/remove unnecessary config
702d6b8 Remove broken ESLint tests
6b4c4ca Upgrade outdated dependencies
bdeb86f remove deprecated rule examples [skip ci]
52b4a13 update readme [skip ci]
0e5aca3 chore(package): update eslint-config-babel to version 6.0.0 (#433)
781dc77 Update to use Node 4 features (#425)
265d219 chore(package): update eslint-config-babel to version 4.0.0 (#430)
e6af5c5 add badges [skip ci]
a91a9d0 Revert "use *" (#426)

There are 17 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of commander is breaking the build 🚨

The dependency commander was updated from `2.18.0` to `2.19.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

commander is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ ci/circleci: CircleCI is running your tests (Details).
❌ continuous-integration/travis-ci/push: The Travis CI build is in progress (Details).
❌ semaphoreci: The build failed on Semaphore. (Details).

Release Notes for v2.19.0

Removed newline after Options and Commands headers (#864)
Bugfix - Error output (#862)
Fix to change default value to string (#856)

Commits

The new version differs by 6 commits.

78b7dbd version bump 2.19.0
6aafa20 prefixed error messages with "error:"
6c0c1f6 removed newline above and below errors
b6549f2 removed indentation from errors
2c20e91 removed newline after options and commands headers
4c294c1 Fix to change default value to string

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of eslint-plugin-import is breaking the build 🚨

The devDependency eslint-plugin-import was updated from `2.14.0` to `2.15.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-import is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ ci/circleci: Your tests are queued behind your running builds (Details).
❌ semaphoreci: The build failed on Semaphore. (Details).
❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 34 commits.

767f01a bump to v2.15.0
038d668 bump webpack resolver to v0.11.0
20a8f3b bump utils to v2.3.0
1e4100d changelog note for #1261
548ea02 added support for argv parameter of webpack`s config-as-a-function (#1261)
fcf2ce7 Merge pull request #1254 from ljharb/travis
64d9be7 allow_failures for dicey Node/ESLint intersection
73080d0 dep-time-travel: use older versions of dependencies
05c3935 repair no-deprecated for ESLint* 5
10c9811 node 4 fix for test util
f165237 ah geez, bumping babel-eslint breaks no-amd/no-cjs
acfb6e9 jk, test against eslint 2/3 but skip Typescript tests.
b686f9d drop ESLint 2/3 from Travis/Appveyor
cf1f6f4 [Deps] update debug, eslint-import-resolver-node, has, lodash, minimatch, resolve
d290a87 [Dev Deps] update babylon, coveralls, eslint-import-resolver-typescript, gulp, linklocal, nyc, redux, rimraf, sinon, typescript-eslint-parser

There are 34 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of mocha is breaking the build 🚨

Version 3.4.0 of mocha just got published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	3.3.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ ci/circleci CircleCI is running your tests Details,- ❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details,- ❌ semaphoreci The build failed on Semaphore. Details

Release Notes

v3.4.0

Mocha is now moving to a quicker release schedule: when non-breaking changes are merged, a release should happen that week.

This week's highlights:

allowUncaught added to commandline as --allow-uncaught (and bugfixed)
warning-related Node flags

🎉 Enhancements

#2793, #2697: add --allowUncaught to Node.js (@lrowe)
#2733: Add --no-warnings and --trace-warnings flags (@sonicdoe)

🐛 Fixes

#2793, #2697: fix broken allowUncaught (@lrowe)

🔩 Other

#2778: Add license report and scan status (@xizhao)
#2794: no special case for macOS running Karma locally (@boneskull)
#2795: reverts use of semistandard directly ([#2648]) (@boneskull)

Commits

The new version differs by 9 commits0.

7554b31 Add Changelog for v3.4.0
9f7f7ed Add --trace-warnings flag
92561c8 Add --no-warnings flag
ceee976 lint test/integration/fixtures/simple-reporter.js
dcfc094 Revert "use semistandard directly"
93392dd no special case for macOS running Karma locally
4d1d91d --allow-uncaught cli option
fb1e083 fix allowUncaught in browser
4ed3fc5 Add license report and scan status

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of rimraf is breaking the build 🚨

The devDependency rimraf was updated from `2.6.2` to `2.6.3`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

rimraf is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ semaphoreci: The build failed on Semaphore. (Details).
❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
❌ ci/circleci: Your tests failed on CircleCI (Details).

Commits

The new version differs by 6 commits.

9442819 2.6.3
42fe369 autopublish scripts
21fd3df bin test
8f1d3a1 update tap and glob for security stuff
f0bc3a1 update tap, add package-lock
692022b travis node version updates

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

tomoat / koa2-generator Goto Github PK

koa2-generator's Introduction

koa-generator

Installation

Quick Start

Command Line Options

License

koa2-generator's People

Contributors

Stargazers

Watchers

Forkers

koa2-generator's Issues

The devDependency supertest was updated from 3.3.0 to 3.4.0.

Middlewares

Version 7.2.3 of babel-eslint just got published.

The devDependency bluebird was updated from 3.5.2 to 3.5.3.

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

Version 7.2.0 of babel-eslint just got published.

New Feature

Bug Fix

Internal/Docs

The dependency commander was updated from 2.18.0 to 2.19.0.

The devDependency eslint-plugin-import was updated from 2.14.0 to 2.15.0.

Version 3.4.0 of mocha just got published.

🎉 Enhancements

🐛 Fixes

🔩 Other

The devDependency rimraf was updated from 2.6.2 to 2.6.3.

Recommend Projects

Recommend Topics

Recommend Org

The devDependency supertest was updated from `3.3.0` to `3.4.0`.

The devDependency bluebird was updated from `3.5.2` to `3.5.3`.

The dependency commander was updated from `2.18.0` to `2.19.0`.

The devDependency eslint-plugin-import was updated from `2.14.0` to `2.15.0`.

The devDependency rimraf was updated from `2.6.2` to `2.6.3`.