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

@hrbolek/uoisfrontend-all

v0.4.20

Published

Based on React, developed with vite stack.

Downloads

306

Readme

Autogenerated UI

Based on React, developed with vite stack.

Automatic generation

This is autogenerated. To regenerate at any time you can execute js script in project root

node tools/gen_ui.js

The result should be run with (see package.json)

npm run dev

What is generated

There are set of templates stored at ./tools/templates.

  • The AppRouter.jsx file / template is explicitly generated
  • From the directory ./tools/Pages all files / templates are generated
  • From the directory ./tools/Components all files / templates are generated
  • From the subdirectory ./tools/Components/SubObjectComponents all files / templates are generated
  • From the subdirectory ./tools/Components/SubVectorComponents all files / templates are generated

What data are used for generation

There is file ./tools/introspectionresponse.json which contains the response to introspection query. This is loaded, parsed somehow and used as source to generate source codes.

This does not works for all graphql cases. There are some limitations:

  • It is expected that Query type has ById fields with one argument (id: UUID!) which returns optional single object, this set of fields is used to generated pages.
  • It is expected that graphql types are named like UserGQLModel, GroupGQLModel etc.
  • ...

What generated source code offers

This depends on templated stored in directories as mentioned above, but

  • For types there are
    • Lazy wrapper which allows to wrap a component to create new component which asks for data from graphql server
    • Link which is clickable and which navigate to appropriate Page
    • MediumCard displaying Scalar attributes
    • LargeCardLayout and LargeCard displaying MediumCard and also cards for Scalar fields and Vector fields
    • Set of Tables displaying Vector fields
    • ...
  • For pages there are
    • Pages for each type

Post editing of generated source code

Since all generated source files have its hash (same file name with extra extension .hash), they are checked for changes. If the source code hash is different than stored, this file is not generated / overriden. Also there is message about this skip.