Credit the original create-angular-app author and send him the link when the scaffolder ships

Open
  • Is something wrong?
#23 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
documentation, release

Research direction

Read #14 for the scaffolder naming decision and #18 for the release checklist, then check the README and release instructions those issues identify. Confirm the release plan uses version 3.0.0 or later and includes the promised credit and email follow-up. Done when the README credit is published and the release checklist records the npm and email steps; the email follow-up depends on publication.

Written by the indexing model from the issue text.

Description

documentation

On 7 November 2026, Vitalii Semianchuk (npm user fix2015) handed over the npm name create-angular-app to me. Until then it held his AngularJS boilerplate; the last version was published in June 2022. On 9 November I became the sole owner on npm. I promised him two things in return, and this issue tracks both so they don't get lost when the scaffolder ships.

What I promised

  1. Credit his original package in the README of whatever we publish as create-angular-app. He accepted the offer ("yep").
  2. Email him the link once the new scaffolder is out. I wrote: "I'll send you a link when it's out." The thread is in my inbox under "Taking over the create-angular-app npm name?".

Done when

  • The create-angular-app README has a short "History" or "Credits" section. It says the name previously held Vitalii Semianchuk's AngularJS boilerplate, that he transferred it in November 2026, and that his versions (1.1.0 to 2.0.0) are still on npm and still install for anyone who pins them. It links his npm profile: https://www.npmjs.com/~fix2015.
  • The first version we publish is 3.0.0 or later: his last version is 2.0.0, so a new major keeps anyone on ^2 or older from picking up the new scaffolder by accident.
  • After that version is on npm, reply in the same email thread with the npm page link and the README link.
  • Optional: deprecate his old versions with a message that points to the new scaffolder (npm deprecate create-angular-app@"<3.0.0" "..."). Only do this if he's fine with it.

Related

  • #14: the scaffolder itself (@push-based/create-ngp). Decide whether create-angular-app replaces that name or points to it.
  • #18: releasing the scaffolder. Add the steps above to that checklist.
Dominant language
TypeScript
Stars
7
Forks
1
Avg merge
12h 24m
Merged PRs (30d)
13

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from push-based/vite-plugin-ngp

All issues in push-based/vite-plugin-ngp

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.