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

eval-expression

v1.0.0

Published

Evaluate an expression and get what you expect.

Downloads

119

Readme

Build statusDavid DM

eval-expression

Evaluate an expression and get what you expect.

Be warned: Take all precausions which apply to using eval. eval-expression is no safer, no more performant and no easier to debug.

But it is more predictable. And, just as eval, it sometimes is useful for rapid prototyping.

Installation

> npm install eval-expression

Usage

var evalExpression = require("eval-expression");


// `eval` fails with function expressions – `evalExpression` handles them.
var sayHello = evalExpression('function () {console.log("Hello!");}');
sayHello();  // Logs: Hello!

// `eval` fails with object literals – `evalExpression` does what you expect.
var fruit = evalExpression('{sort: "pear"}');
fruit;  // Outputs: {sort: "pear"}


// You can access variables in the current scope.
console.log(evalExpression("fruit"));  // Outputs: {sort: "pear"}


// `evalExpression` is only intended to evaluate expressions, not other
// statements.
var tasty;

// So don't do this:
evalExpression('if (fruit.sort == "pear") {tasty = true}');  // Throws

// Do this instead:
tasty = evalExpression('fruit.sort == "pear" ? true : false');  // Outputs: true

// …or even:
tasty = evalExpression('fruit.sort == "pear"');  // Outputs: true

API

evalExpression(expression)

expression

Type: String
Required

A single expression. It will be evaluated in an enclosed scope.

Why use it

eval doesn't always work as you'd expect. See these cases:

License

MIT © Tomek Wiszniewski.