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

@nljms/toy-robot-challenge

v1.0.1

Published

This is a typescript implementation of the toy robot challenge. This project uses es6 module and is being transpiled by [babel](https://babeljs.io/). I'm using node 14.15.0 in this project so there would be a posibility that you might encounter some error

Downloads

4

Readme

Getting Started With Toy Robot Challenge publish-npm-package publish-npm-package

This is a typescript implementation of the toy robot challenge. This project uses es6 module and is being transpiled by babel. I'm using node 14.15.0 in this project so there would be a posibility that you might encounter some error while trying to install the dependecies. You can use nvm

Implementation

I've used different architectural patterns in this project.

  • Singleton
    • I setup a store which serves as the singe source of truth for this project. Most of the services uses the single instance of RobotMovementStore
  • Event Sourcing
    • I used a store in this project to persist and rebuild the history of valid command inputs that are handled in this system
  • Dependency Injection
    • Although it's not the usual kind of implementation, I am always a fan of dependency injection. In this approach I am free to abstract things and spread it out into different domains.

Folder structure

├── README.md
├── jest.config.js
├── package.json
├── src
│   ├── commands
│   │   ├── __tests__
│   │   │   ├── command.spec.ts
│   │   │   ├── parseInstruction.spec.ts
│   │   │   └── readFile.spec.ts
│   │   ├── command.ts
│   │   ├── parseInstruction.ts
│   │   └── readFile.ts
│   ├── domain
│   │   ├── index.ts
│   │   ├── robot.ts
│   │   ├── store.ts
│   │   └── table.ts
│   ├── errors
│   │   ├── InvalidCommandException.ts
│   │   ├── InvalidDirectoryException.ts
│   │   ├── InvalidMovementException.ts
│   │   ├── OutOfBoundsException.ts
│   │   └── index.ts
│   ├── index.ts
│   ├── types
│   │   ├── enum.ts
│   │   ├── index.ts
│   │   └── interface.ts
│   └── utils
│       ├── cli.ts
│       ├── index.ts
│       └── logger.ts
├── tsconfig.json
└── yarn.lock

Start development

There were two arguments needed to run this application.

  • -i [--input] - uses cli to handle input commands
  • -d [--directory] - uses fileDirectory to read commands inside a readable file.
# install dependencies
yarn

# running it locally
yarn start -i # or use --input if you want to use it verbosely

# or file based entry
yarn start -d <file-to-path>  # or use --directory if you want to use it verbosely

# run test
yarn test

Deployment

I'm using github workflows to deploy this to npm