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 🙏

© 2026 – Pkg Stats / Ryan Hefner

salestock-backend-ta

v0.0.1

Published

Salestock Backend Technical Assigment

Readme

Salestock Backend Technical Assigment

This is The Salestock Backend TA. They give me two cases, and I choose the product and category management with hierarchical tree data for category. The end goal of this TA is to build API endpoint for the case that production-ready grade.

The mandatory assesment points is

  1. REST API routing design
  2. Apps modeling and abstraction skill

which 2 of this assesment points should be perfect 5.

I know, you may think that those assesment points is sounds very subjective. Because different organization have different perspective about how they design REST API and modeling the apps. So, it's hard to have 5 points on this subjective one.

I try to ask them to elaborate more and if there is exists some kind of style guide from their organization that I can use as reference. But, I got no answer from them.

I feel a litle bit strange. I want create API endpoint that fit their culture, but I have no clue. I don't know if it's ever going to work. I just build what I believe that this is the best approach of REST API and Apps modeling.

The technology constraint is they only allowed me to use Scala or Nodejs. This is doen't matter actually. I can't write any Scala because my litle notebook doesn't have enough memory to run JVM, it's ironic. I have build a several in-house production apps in Nodejs and it's very hard to manage, especially for team.

Just my 2c, they should try Go programming language and get the hell out from javascript-callback-hell + complexity-of-NPM-modules. Also, The core community of Nodejs is too political. It's to risky to bet the core technology of the company in Nodejs. I hope their technical director know that.

Status

WIP

Demo

TODO: screencast should be enough?

API

TODO:

Categories
GET /categories - fetch all categories
POST /categories - create a new category
GET /categories/:id - fetch a single category
PUT /categories/:id - update category
DELETE /categories/:id - delete category

Product
GET /products - fetch all products
POST /products - create a new product
GET /products/:id - fetch a single product by id
PUT /products/:id - update products
DELETE /products/:id - delete product
GET /products/category/:id - fetch all prpducts from a single category

License

BSD 3-clause