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

openfpga-validator

v0.7.0

Published

Script which validates OpenFPGA core zips

Downloads

7

Readme

openfpga-validator

Script which validates OpenFPGA core zips

Usage

To run, do:

npx openfpga-validator@latest check <path_to_zip>

(you'll need node installed but after that it'll be a 1 line thing)

It'll return the errors, warnings, & recommendations

Can check for more options with

npx openfpga-validator@lastest check --help

Adding checks

If you want to add a check then:

  • Raise an issue (with examples of fail / pass criterion) & I'll get to it eventually

Or, if you want to do it yourself

  • if it doesn't fit into one of the files which already exist in the src/checks folder then create a new one
  • export a function of the type CheckFn
  • decide on the level:
    • If it would break on the Pocket itself, or goes against a must in the Analogue Docs, then it's an error
    • If it would probably break an updater, or cause a user to have to do extra work, but doesn't go against anything in the Analogue Docs it's a warning
    • If it's just nice to have - or it's a convention followed by other cores - then it's a Recommendation
  • If you can specify the part of the Analogue Docs which talk about the issue then include the URL in the message
  • add an await for it to the main index.ts
  • Add a "good" example to the good folder in test_zips and a "bad" example in the bad one
  • run npm test -- -u to update the snapshots within the tests & check they look as expected
  • Raise a PR, I'll merge, bump the version, and do a release

To run locally

Doing

npm run run check <path_to_zip>

Will build the TS files & run it as if a user's done npx openfpga-validator check <path_to_zip>