Convert to a monorepo

[ForbesLindesay]

I think a monorepo (but still with separate npm packages) will make development on pug much easier & faster. I propose that we move the following packages into a single monorepo:

• pug
• pug-lexer
• pug-parser
• pug-load
• pug-linker
• pug-code-gen
• pug-filters
• pug-runtime
• pug-walk
• pug-strip-comments
• pug-error
• pug-attrs

I propose that we keep the following packages separate:

• pug-ast-spec
• constantinople
• doctypes
• doc-down
• is-expression
• is-expression-babylon
• pug-www
• pug-en, pug-zh-cn etc.
• void-elements
• babel-plugin-transform-react-pug
• gulp-pug
• pug-cli
• pug-lint
• with
• then-pug (still currently published as then-jade but needs renaming)
• token-stream
• babel-plugin-transform-with
• babylon-walk
• all pug plugins
• pug-lint-config-migration-v2
• pug-logo
• react-pug (still currently published as react-jade but needs renaming)
• pug-plugin-dynamic-include
• pug-source-gen
• pug-plugin-debug-line
• brjade
• js-stringify

I think some of these packages will probably move into the monorepo over time if it proves successful. We will continue to follow semver individually in each package we release.

[ForbesLindesay]

Each of the repositories now in the monorepo needs to have issues coppied & pull requests coppied over to the monorepo, have issues disabled, and be replaced with a simple README explaining where the project has moved to:

• [ ] pug-lexer
• [ ] pug-parser
• [ ] pug-load
• [x] pug-linker
• [x] pug-code-gen
• [x] pug-filters
• [ ] pug-runtime
• [x] pug-walk
• [x] pug-strip-comments
• [ ] pug-error
• [ ] pug-attrs

Look at pug-walk for an example of what needs doing.

[jeromew]

I migrated https://github.com/pugjs/pug-code-gen but I don't seem to have rights to disable new issues on this repo.

[ForbesLindesay]

Thanks, I've disabled them.

[OwnageIsMagic]

https://github.com/blog/2460-archiving-repositories