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

@wmde/eslint-config-wikimedia-typescript

v0.2.12

Published

ESLint config for TypeScript following Wikimedia code conventions.

Downloads

4,773

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

tarrowtarrowmanickimanickithiemowmdethiemowmdelucaswerkmeisterlucaswerkmeistermariushochmariushochwmdebotwmdebotjakob_wmdejakob_wmdedarthmondarthmonitamar.wmdeitamar.wmdenoa_wmdenoa_wmde

Keywords

style guideeslinteslintconfigwikimedia

Readme

eslint-config-wikimedia-typescript

ESLint config for TypeScript following Wikimedia code conventions - the idea is to make this repository here obsolete in the medium term and upstream these rules.

Release instructions

To make a new release:

  1. Bump the version number in a pull request. (Edit package.json manually, then run npm install to update the version number in package-lock.json.) The usual commit message is “Bump version to 1.2.3”. Example pull request.

  2. Get that pull request reviewed and merged.

  3. Tag the merge commit locally. A “lightweight” tag is usually enough: git pull, then git tag v1.2.3.

  4. Push the tag. git push origin v1.2.3

  5. Turn it into a proper release on GitHub: draft a new release. Example release.

  6. Once the GitHub release is published, it should be automatically published to NPM via GitHub Actions.

  7. Submit a Gitlab change to ci-tools/libup-config to update the version of the package in releases.json. (Source; replace with an example once available.)