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

interpreting

v0.0.1

Published

Require any file extension of interpret dictionary.

Downloads

1

Readme

interpreting

Require any file extension of interpret dictionary.

Version npm NPM Week Downloads Build Status Dependencies Dev Dependencies JavaScript Style Guide

Require using the dictionary of file extensions and associated module loaders from interpret dictionary. Useful, for example, to allow config files in any supported file extension, like requiring webpack config file just doing interpreting('./webpack.config').

Available file extensions and the associated module loader:

  • .js: none
  • .babel.js: babel-register
  • .buble.js: buble
  • .cirru: cirru-script
  • .cjsx: node-cjsx
  • .co: coco
  • .coffee: coffee-script
  • .coffee.md: coffee-script
  • .csv: require-csv
  • .eg: earlgrey
  • .iced: iced-coffee-script
  • .iced.md: iced-coffee-script
  • .ini: require-ini
  • .json: none
  • .json5: json5
  • .jsx: babel-register
  • .litcoffee: coffee-script
  • .liticed: iced-coffee-script
  • .ls: livescript
  • .node: none
  • .toml: toml-require
  • .ts: ts-node
  • .tsx: ts-node
  • .wisp: wisp
  • .xml: require-xml
  • .yaml: require-yaml
  • .yml: require-yaml

Install

npm

npm install --save interpreting

yarn

yarn add interpreting

Usage

const interpreting = require('interpreting')
// or
import interpreting from 'interpreting'

Examples

// config.babel.js
export const value = 1
interpreting('./config')
// { value: 1 }

API

interpreting(path, [options])

If path or path.* not exists, returns null or throws a error if options.required is true.

path

  • Type: string string[]

File or list of files to require.

options

required
  • Type: boolean
  • Default: false

If true, at least one file must be found.

multiple
  • Type: boolean
  • Default: false

If false returns the first found file. Otherwise, returns an array with all files founded.

join
  • Type: boolean
  • Default: false

If true and multiple is true, returns the Object.assign() result for all files.

Resources

  • interpret - A dictionary of file extensions and associated module loaders.

Authors

License

MIT