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

any-eval

v1.0.0

Published

Super handy eval of anything

Downloads

110

Readme

any-eval

Super handy eval of anything.

Supports JS-expression, CommonJS module contents and JSON/JSON5.

NPM Status Travis Status Coverage Status Dependency Status

Install

$ npm install --save any-eval

Usage

JS-expression

const anyEval = require('any-eval');

anyEval('42 * 42'); // 1764

CommonJS

const anyEval = require('any-eval');
const moduleContents =
`
    const package = require('./package.json');

    module.exports = {
        name: package.name
    };
`;

anyEval(moduleContents, './index.js'); // filename need to provide required info to resolve relative paths inside evaluating code

// ➜ { name: 'any-eval' }

JSON

const anyEval = require('any-eval');
const jsonContents = '{ "name": "any-eval" }';

anyEval(jsonContents, 'my.json'); // filename need to `any-eval` determinate json format by extention

// ➜ { name: 'any-eval' }

JSON5

const anyEval = require('any-eval');
const jsonContents = "{ name: 'any-eval' }";

anyEval(jsonContents, 'my.json5'); // filename need to `any-eval` determinate json format by extention

// ➜ { name: 'any-eval' }

API

anyEval(contents[, filename, context])

contents

Type: string

The JS-expression, CommonJS module contents or JSON/JSON5 contents.

filename

Type: string

The path to file which contents we execute.

The any-eval determinate format by extension. If filename ends with .js, its contents will be evaluating with vm. If filename ends with .json, its contents will be parsing with JSON.parse. If filename ends with .json5, its contents will be parsing with json5.

By default expected JS-expression or CommonJS module contents.

const anyEval = require('any-eval');

anyEval('42 * 42'/* js by default */); // 1764
anyEval('42 * 42', 'my.js'); // 1764
anyEval('{ "name": "any-eval" }', 'my.json'); // '{ name: 'any-eval' }'
anyEval("{ name: 'any-eval' }", 'my.json5');  // '{ name: 'any-eval' }'

To evaluating CommonJS module contents filename is required to resolve relative paths inside evaluating code.

const anyEval = require('any-eval');
const moduleContents =
`
    const package = require('./package.json'); // to resolve this require need to know the path of current module (./index.js)

    module.exports = {
        name: package.name
    };
`;

anyEval(moduleContents, './index.js'); // filename need to provide required info to resolve relative paths inside evaluating code

Internally any-eval will resolve passed relative paths using the place it's called (like require do).

It may spend additional processor's time on it, so better to pass in absolute path.

const fs = require('fs');
const anyEval = require('any-eval');

// For example, current path is "/repos/project/lib/file.js".
const modulePath = '../files/another.js';
const moduleContents = fs.readFileSync(modulePath, 'utf-8');

// '../files/another.js' will be resolved to '/repos/project/files/another.js'
anyEval(moduleContents, modulePath);

context

Type: Object

The object to provide into execute method.

If context is specified, then module contents will be evaluating with vm.runInNewContext.

If context is not specified, then module contents will be evaluating with vm.runInThisContext.

With context you can provide some like-a-global variables into any-eval.

const anyEval = require('any-eval');

const secretKey = '^___^';
const contents = 'module.exports = secretKey;';

anyEval(content, { secretKey }); // '^___^'

Related