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

open-standards

v0.1.0

Published

An open set of standard questions every developer should know in their respective fields.

Downloads

5

Readme

The CSPA Open Standards

CSPA is a tech company dedicated to streamlining the job market. This open source project is part of our efforts to find answers to some difficult questions:

  • Why do programmers have to repeatedly take widely-varying and subjectively written technical tests each and every time they interview at a company?
  • Why do companies have to spend time reviewing each candidate as if from scratch?
  • What does it mean to be competent in a language, framework, or technology? Can we encode these requirements in a precise, standardized way?

These are not easy questions to answer! And we're not certainly not trying to do it alone. If you would like to input your expertise, please apply for the Technical Steering Committee.

The JavaScript Open Standard

The first tech we're targeting is the ever-increasingly ubiquitous JavaScript. JavaScript has a long history of quirks, great features, and misunderstandings – it's the perfect language to target first.

By providing these open standards, we hope to provide empirical guidance to programmers on what exactly they need to learn to start working in the industry. Because they are open, everyone in the world is free to not only write educational materials to teach these topics, but also to recognize them as the standard of competence when hiring new software developers for their team.

Our ultimate goal is to make the software industry a better place!

Question Format

Each set of questions is an xml file with several questions in them. Here are the formats you can expect:

<!-- A group of questions that are highly similar. -->
<group name="My Group"></group>

<!--
  A multiple-choice question is a question where the user
  selects a single answer from a set of pre-defined choices.
  This is the default question type.
-->
<question type="multiple-choice">
  <!--
    The contents of the question ask;
    This is common across all questions
  -->
  <body>What is 2 + 2?</body>

  <!--
    A multiple-choice question MUST have at least one choice-group.
    A choice-group name must be unique within its question.
    The default name is "default".
  -->
  <choice-group name="default">
    <!--
      Choices can be marked with the answer attribute.
      Exactly one MUST be marked as answer.
    -->
    <choice>2</choice>
    <choice answer>4</choice>
  </choice-group>
</question>

<!--
  A line-numbers question is a question where the user selects
  one or more lines from a block of code.
-->
<question type="line-numbers">
  <body></body>

  <!--
    The code to select lines from.
    The default language is "javascript".
  -->
  <code lang="javascript"></code>

  <!--
    A comma-separated list of line numbers.
    If the `optional` attribute is present,
    the user will be presented a button with
    the text "None of the above"
  -->
  <answer></answer>
</question>