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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@agungkes/typescript-project-generator

v2.6.15

Published

A TypeScript initial configuration for web projects

Downloads

33

Readme

TypeScript project generator

This project has the goal to create a basic setup for a TypeScript project. It will create many files that are usually created manually. Currently the following files are being created:

  • .env
  • .eslintignore
  • .eslintrc.js
  • .gitignore
  • .prettier
  • changelog.md
  • Dockerfile
  • heroku.yml (optional)
  • LICENSE (MIT as example)
  • nodemon.json
  • package.json
  • readme.md
  • tsconfig.json
  • webpack.config.js

The following questions will be asked to the user:

  • Yarn or npm?, only one of them is valid.
  • Project name:, at least one character must be provided.
  • Project description:, at least one character must be provided.
  • Author:, at least one character must be provided.
  • Email:, a correct email address must be provided.
  • Project version (0.1.0): the initial version of the project, 0.1.0 as default.
  • Select your license [1...7]:, the license you have chosen for the project.
  • License year (current year):, the year where your license starts, current year as default.
  • Will this project be deployed with Heroku? [y/n]:, yes or no question, only y or n is accepted. This is not case sensitive.
  • Would you like to implement a express server with mongoose? [y/n]:, yes or no question, only y or n is accepted. This is not case sensitive.

What is new?

Please check the changelog.md file.

With express or without it?

Without express

A src folder will be created with the following structure:

📦src
 ┗ 📜index.ts

With express

A src folder will be created with the following structure:

📦src
 ┣ 📂controllers
 ┃ ┗ 📜users.ts
 ┣ 📂custom
 ┃ ┣ 📜error.ts
 ┃ ┣ 📜express.request.ts
 ┃ ┣ 📜express.response.ts
 ┃ ┗ 📜global.variables.ts
 ┣ 📂dto-interfaces
 ┃ ┗ 📜users.dto.ts
 ┣ 📂models
 ┃ ┗ 📜users.ts
 ┣ 📂network
 ┃ ┣ 📜response.ts
 ┃ ┣ 📜routes.ts
 ┃ ┗ 📜server.ts
 ┣ 📂routes
 ┃ ┣ 📜home.ts
 ┃ ┗ 📜users.ts
 ┗ 📜index.ts

Some considerations:

  • If you choose this option, now you are able to run a server that has one main route, home (/), and another one, users (/users or /users/:userId).

  • To connect your server with your MongoDB database, you need to provide your uri in the .env and uncomment the indicated lines in the src/network/server.ts file.

  • Once you have done that, now you can perform the following HTTP REQUEST: GET, POST, PATCH and DELETE.

  • In order to use the global variable declared in the src/custom/global.variables.ts file, you have to add the following lines in the external file you want to use it:

    import { CustomNodeJSGlobal } from "/direction/to/global.variables/file";
    declare const global: CustomNodeJSGlobal;

    Now, your are able to use the global variable.

  • The provided project structure is inspired in my personal experience as Node.js developer and the Nest framework.

  • The server is fully tested and has no errors (at least for now), feel free to report one here.

  • Support for windows and linux platforms is available.

  • Check the content of those files, here:

Finally, git will be initialized and a list of libraries will be installed. Check the notes.

Prerequisites

You need to have internet connection to install the packages and to get the license from this web page.

Installation

This project was intended to be installed globally, not locally, and also to initialize projects, be aware of that, you may broke something in your current working directory.

In order to install this package, run the following command in your terminal:

npm i -g typescript-project-generator

Usage

Once you have installed the package, please run the following command in your terminal:

tpg

This will guide you in a process to initialize your new project, asking you the questions shown above.

Notes

Here is the list of the packages that are being installed, as devDependencies:

Optionals

As devDependencies:

As dependencies:

Feel free to contribute to this project. Every contribution will be appreciated.

Author

  • Anthony Luzquiños - Initial Work - Documentation - AnthonyLzq.