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

nest-ts-code-gen

v1.0.2

Published

a code generator to generate nest template files and typescript definition files

Downloads

3

Readme

what it is

nest-ts-gen is a code generator to generate back-end nest template code(controller, service, module) and front-end ts type, see in the demo demo/

requirement

  1. contract/: write back-end type and controller mapping configuration in the contract folder
  2. setup codeGen in your code: setup mapping, output folder and output file name
  3. mkdir all your output folder, make sure it exist

notification

  1. nest-ts-gen will replace controller output file and module output file, and as you know nest.service is not a template file, so the service file will be keep if exist, and only replace service method and related type :)

mapping config

write the key _config in the mapping config like this:

export default {
  _config: {
    // specify Controller promised common response type, it should be a generic type, so response type will be generated as CommonRes or CommonRes<SomeDto>
    promiseGenericRes: "CommonRes"
  },
  // controller, service, entity => we name it as model name
  model1: {
      // method name
      getStr: {
          // request dto type, you should define it in your contract folder first
          req: 'GetStrRequest'
          // response dto type, define before you write
          res: 'GetStrResponse'
      }
  },
  model2: {
      _config: {
          // stop to generate controller file
          disableController: true,
          // stop to generate entity (in service imports and module imports)
          disableEntity: true
      }
      getStr: {
          // if you don't write req and res, default req: any and res: _config.promiseGenericRes will be generated
      }
  }

and see props in the file src/type/global.ts