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

eslint-plugin-prisma-nestjs-graphql

v0.1.4

Published

eslint plugin for prisma & nestjs & graphql setups to not forget resolvers etc.

Downloads

22

Readme

eslint-plugin-prisma-nestjs-graphql

Goal of the plugin (p):

  • I always forgot some field-resolvers in my graphql resolver files.
  • I wrote myself a little eslint p to check the prisma.schema entities' relations against the field resolvers in my files.
  • Additionally, the p can auto-fix missing resolvers (means it inserts them (quite) the right way).
  • Together with lint --fix it can auto-generate all your (basic) field resolvers.
  • So the overall goal is to save you and me from error-prone, manual field resolver coding.
  • This p will (atm) not check if you implemented all models of your prisma file, just if there is a model resolver => it will check if the field resolvers are there

How to use the p:

  • Install it: npm i -D eslint-plugin-prisma-nestjs-graphql
  • It needs you to also use https://www.npmjs.com/package/prisma-json-schema-generator as generator for your prisma setup.
  • The p will look for a file called prisma/generated/json-schema.json which should be generated by the prisma-json-schema-generator
  • Therefore the generator should look somewhat like that:
...
generator jsonSchema {
  provider = "prisma-json-schema-generator"
  output   = "./generated/"
}
...

Known issues

  • Paths are inflexible
    • Will hopefully be adressed in the future

Related Plugins / Repos / Topics

npm package: https://www.npmjs.com/package/eslint-plugin-prisma-nestjs-graphql prisma-nestjs-graphql resource generator: LINK