npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

generator-typescript-project-generator-by-ridesz

v1.0.14

Published

Re-runnable project generator for TypeScript project generators.

Downloads

117

Readme

Generator TypeScript Project Generator by Ridesz

Re-runnable project generator for TypeScript project generators.

How to start?

Create and clone a GitLab project (https://gitlab.com) then run this in the project folder:

npx generator-typescript-project-generator-by-ridesz@latest

How to continue?

To upgrade and re-run the generator:

npm run project:upgrade

Major version steps can be painfull. Maybe you need to answer some questions. Maybe you need to change some things manually. Please read the console output carefully.

To rerun the generator without upgrade:

npm run project:regenerate

Optional arguments

The generator has some optional arguments (you can combine them):

  • --verbose: print info level messages too
  • --force: overwrite everything without asking confirmation
  • --silent: don't ask questions
  • --regeneratedFolder: custom name for the regenerative folder

Generated setup

  • The version control system is Git
  • The repository is GitLab (private runner support, selfhostin is possible, etc.)
  • The main language is TypeScript
  • EcmaScript module resolution (don't to use commonjs)
  • Don't use JavaScript (unless there is no other way)
  • The package manager is NPM
  • The linter is ESLint and the formatter is Prettier
  • The tesing framework is Jest
  • Git hooks with Husky and lint-staeged
  • Code editor is Visual Studio Code
  • And more... (code duplication check, dead code check, circular imports check, etc.)

Generated folder structure

  • Source files in the src
  • Test files in the test
  • Script files in the script (for tools like build, check, etc.)
  • Configuration files in the config
  • Git ignored report outputs in the report
  • A special volatile folder which will be purged and recreated for every generator run (generated by default)
  • A few other files in the root (package.json, tsconfig.json, README.md, .gitignore, .gitlab-ci.yml, etc.)

About the re-runnability

There is a special volatile folder. It will be deleted and recreated by every run of the generator. This folder contains recommended project parts granted by the generator and it can change after time.

Other files can be also affected by generator runs: dependencies and scripts in package.json, default values for some files if they are missing (or the target folder is empty), etc.

Starting from an existing project

Not supported. You can try to remove most parts of your project to avoid conflicts, run the generator and bring back carefully what you need with your version control system. But this is not really a recommended way.

Yeoman is under the hood

This generator is just a Yeoman generator (https://yeoman.io/) with extra steps.

You can install it globally and run it with Yeoman. (the generator- prefix missing for reason):

npm i -g generator-typescript-project-generator-by-ridesz@latest && npx yo typescript-project-generator-by-ridesz

Alternative way with temporary install:

npx --package=yo@latest --package=generator-typescript-project-generator-by-ridesz@latest -c "yo typescript-project-generator-by-ridesz"

The global install is required by Yeoman, just like the "generator-" prefix.

About the development

Maybe the easiest way is a global install after your changes:

npm pack && npm i -g ./generator-typescript-project-generator-by-ridesz-1.0.14.tgz

Then you can run it in the target project folder:

npx generator-typescript-project-generator-by-ridesz

The npm link and npx run yeoman:regenerate were broken for me.

Please be carefull, globally installed variants can cause conflicts.

More info in the backbone project: README_DEV.md