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

@molo17/technical-tests

v0.3.3

Published

As per our hiring process, candidates shall perform a demo project that will be evaluated and discussed during the interview.

Downloads

39

Readme

MOLO17 Technical Tests

As per our hiring process, candidates shall perform a demo project that will be evaluated and discussed during the interview.

Available technical tests:

Developing and building the technical tests

First of all, you need to install the dependencies using yarn.

To start watching the markdown files and build the PDF files on changes, run the start script.

To build the final PDF files, run the build script.

If you need to add a technical test, simply add a new markdown file in the src folder. The scripts will automatically build the PDF for the new file too.

Deploying and viewing the deployed technical tests

First of all, you need to update the package version on the package.json.

After that, you just need to publish the new package version on npm. To do that, you can either:

  • Let the CI do the work by pushing a commit on master with the following pattern:

    release: <new version>

    e.g. release: 1.0.0

  • Manually publish it by running:

    yarn publish --non-interactive --access public --new-version <new version>

    e.g. yarn publish --non-interactive --access public --new-version 1.0.0

After the deploy step you should be able to view a technical test by executing npx @molo17/technical-tests view <technical test>

e.g. npx @molo17/technical-tests view fullstack

License

Copyright 2021 MOLO17 SRL

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.