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

wertik-js

v3.3.3

Published

Wertik is a tiny Node JS framework that helps you set up servers with support for

Downloads

33

Readme

Wertik-JS V3

Wertik is a tiny Node JS framework that helps you set up servers with support for

  • MySQL Database
  • Emailing
  • GraphQL
  • Modules
  • Rest Api
  • Storage
  • Sockets
  • Cron Jobs
  • Redis
  • Logger

Installation

You can install wertik-js by using yarn or npm:

Yarn

yarn add wertik-js

Npm

npm install wertik-js

Setting up server

To start wertik-js server you need to import wertik and start it:

import wertik from "wertik-js/lib/"

weritk({
  port: 1200,
})

In your console you will see something like this:

Wertik JS app listening at http://localhost:1200

If you visit http://localhost:1200, you will see a response like this:

Cannot GET /

🚀 You have successfully started wertik server. There is nothing in wertik app right now. Let's make it interactive by adding:

  • MySQL Database
  • Mailer
  • GraphQL
  • Modules
  • Rest Api
  • Storage
  • Sockets
  • Cron Jobs
  • Redis

Accessing Wertik Inside GraphQL Resolver and Express Handler

You can access Wertik instance inside GraphQL and Express handler through:

  • Express
app.get("/somepath", (req, res) => {
  console.log(req.wertik) // Wertik App
  res.send("Some Info")
})

For more please see This line.

  • GraphQL Resolver
function Resolver(_, args, context, info) => {
  console.log(context.wertik); // Wertik App
  return "Some Info"
}

For more please see: This line

With keyword Wertik you can access everything that lies inside wertik from database, modules, sockets, mailer, cron jobs to everything in Wertik app.

Why you should use Wertik JS

Wertik JS lightens up your app with different features, Wertik can be helpful for small projects such as task management or a blog application. With modules with Wertik JS, you can easily create modules with crud operations. Furthermore, Wertik JS can lighten up your app with useful features such as Redis, Sockets, Database such as Mysql, Queue Management, Storage, Cron Jobs, and other useful features.

How Wertik JS works internally

Wertik JS v3 is setup in a clean way and easy way. Here is the main file which initializes Wertik JS: Show File.

You can check the code and if you find something that needs to be changed, you can create a new Issue here.

Did you find a grammatical mistake in the documentation?

If you came across a grammatical mistake please create a new issue with more details in the description: here.

Contribute & Support

Pull requests are welcome. If you have discovered a bug or have a feature suggestion, feel free to create an issue on GitHub.

If you'd like to make some changes yourself, see the following:

  • Fork this repository to your own GitHub account and then clone it to your local device
  • Make sure yarn is globally installed (npm install -g yarn)
  • Run yarn to download required packages.
  • Build and start the application: yarn dev-next
  • If you contributed something new, run yarn contrib:add to add yourself to the contributors list
  • Finally, submit a pull request with your changes!