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

jsconfig-init

v1.0.2

Published

Turn on transpile-free type hinting for your vanilla JS projects #JSWithTypes

Downloads

31

Readme

jsconfig-init

Turn on transpile-free type hinting for your vanilla JS projects #JSWithTypes

  1. Create a plain JavaScript project
    npm init
  2. Turn on type linting 💪
    # Create a properly configured `jsconfig.json`
    npx jsconfig-init
  3. Profit!

Works with VS Code out-of-the-box, and Vim + ale.

Layout

Your project will look something like this:

.
├── bin/
├── jsconfig.json
├── node_modules/
│   └── @types/
│       └── node/
├── package-lock.json
├── package.json
├── README.md
├── types.js
└── typings/
    └── overrides/
        └── index.d.ts

Inner Workings

  1. Runs tsc --init with these options:
    npx -p typescript@4 -- \
        tsc --init \
        --allowJs --alwaysStrict --checkJs \
        --moduleResolution node \
        --noEmit --noImplicitAny --target es2022 \
        --typeRoots './typings,./node_modules/@types'
  2. Adds the following keys:
    "include": ["*.js", "bin/**/*.js", "lib/**/*.js", "src/**/*.js"]`
    "exclude": ["node_modules"]
  3. Renames tsconfig.json to jsconfig.json
    (and creates some placeholder files and dirs)

Bonus: npm run lint

You may wish to add common script commands for fmt and lint:

npm pkg set scripts.lint="npx -p typescript@4 -- tsc -p ./jsconfig.json"
npm pkg set scripts.fmt="npx -p prettier@2 -- prettier -w '**/*.{js,md}'"

Bonus: Vim Config

It should Just Work™, but if your vim setup is a little custom, you may want to add or modify a line like this:

~/.vimrc:

let g:ale_linters = {
\  'javascript': ['tsserver', 'jshint'],
\  'json': ['fixjson']
\}