This will allow the generated links to function properly in git forges

Major version 12 is available

currently coming out as the gt and lt encodings

Like push-and-publish without pushing

In order, check

• local git remote (origin)

I'm assuming we can have a top-level .eslintrc.js configuration but have yet to determine the mechanics to make this work

• add watch:compile

Linking (as is done currently) the readme upon generation doesn't keep it in sync, but after deleting and re-making the link (I suspect its important to run typedoc first) does keep the readme in sync.

Do this automatically so the user doesn't have to

https://blog.revathskumar.com/2018/03/nodejs-npm-init-with-custom-values.html

This involves querying the active .npmrc file

https://github.com/dubzzz/fast-check

This may be in the form of a nodemon.json

but I want to

nodemon -e 'ts json' -x 'ts-node $* || true'

perhaps as conveniently as a npm run nodemon -- $*

test.todo('write tests for <%=pkg=>')

https://github.com/typescript-eslint/typescript-eslint

to create a binary

• add bin to package.json (probably just a TODO)
• add shebang to top of src (#!/usr/bin/env node)
• add local-variable block to bottom of src

/* Local Variables: */
/* mode: typescript */
/* End:             */

To raw url just like with github projects

Obvious solution is to build on publish

• means storing build-artifacts in git repos

worth the tradeoff imo, look for a good example to see how this is done

I believe the group is not being parsed-out properly

e.g. when using project name to create method in src/pkg.ts file

Changes

• update install instructions (readme.md)
• update import instructions (readme.md)
• update readme badges
• update package.json with access: public (https://stackoverflow.com/a/43007660/10596482)
• update package.json with name (should include scope)

Scope should be gleaned from
- [ ] default scope (check npm config)

• additionally, query user for scope upon invocation to yo

Which I still prefer for larger projects (end-nodes in the dependency tree)

• strip comments
• no final comma

https://basarat.gitbooks.io/typescript/docs/tips/defaultIsBad.html

I don't find many points valid save the one about reducing typos. That alone is good enough for me

Modifications branch is working though

• in readme
• through yo

• find a suitable templating engine
• wire it in

consider how to upgrade major versions. Might have to just keep updating this generator

As recent versions of typescript don't seem to allow this anymore

The speedup should be righteous

and badge to readme

https://inch-ci.org/github/mimetnet/node-stream-array