feat: add a script to scaffold and bootstrap a new package

[raymondfeng]

We often need to add new packages to loopback-next. Copy/paste is error prone. This script scaffolds a new project under packages or extensions depending on the current directory. Then it uses lerna bootstrap to set up dependencies.

Depends on #4994

Checklist

👉 Read and sign the CLA (Contributor License Agreement) 👈

• npm test passes on your machine
• New tests added or existing tests modified to cover all changes
• Code conforms with the style guide
• API Documentation in code was updated
• Documentation in /docs/site was updated
• Affected artifact templates in packages/cli were updated
• Affected example projects in examples/* were updated

👉 Check out how to submit a PR 👈

[bajtos]

I love the idea of automating the task of creating new packages, I agree the current "copy & paste" process is too error prone.

I feel it's important to write some tests to verify what content the new package contains and even more importantly to verify that it's correctly registered in our monorepo (see https://github.com/strongloop/loopback-next/blob/master/docs/site/DEVELOPING.md#adding-a-new-package).

Without that, I don't see much value in this script, when compared to running lb4 extension && lerna bootstrap manually.

[bajtos]

What if we want to add a regular package (packages/{name}) or even an acceptance test (acceptance/{name}) - is lb4 extension a good command to use?

[raymondfeng]

For regular package, yes. But not for acceptance tests.

[raymondfeng]

Without that, I don't see much value in this script, when compared to running lb4 extension && lerna bootstrap manually.

Please see updated DEVELOPING.md. The script automates most steps except updating CODEOWNER and MONOREPO.md. But we do print out a message after the command finishes.

[raymondfeng]

I'll add the copyright step once #4994 is landed.

[raymondfeng]

I feel it's important to write some tests to verify what content the new package contains and even more importantly to verify that it's correctly registered in our monorepo (see https://github.com/strongloop/loopback-next/blob/master/docs/site/DEVELOPING.md#adding-a-new-package).

Not sure if we want to write tests for internal scripts.

[bajtos]

Thank you for the updates, I'll take another look next week.

[emonddr]

Perhaps update the issue title to match the commit title? To me, they seem like different things. thx.
@raymondfeng ^

[raymondfeng]

@bajtos Since it's an internal script. I went ahead to merge it. Please continue to provide feedback so that we can improve it if necessary.

[bajtos]

@raymondfeng I think this is no longer accurate, now that we are using project references (via #5155)?