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

@optimal/object

v0.1.0

Published

Force V8 to optimize an object's properties or check its status

Downloads

1

Readme

@optimal/object

Build Status Dependency Status npm version Coverage Status

Force V8 to optimize an object's properties or check its status.

Use this when:

  1. the object ends up in slow mode
  2. it's not possible to refactor code to avoid slow mode (such as defining all the properties on it ahead of time and only altering their values, not adding properties, and not deleting them)
  3. an object's properties are accessed often enough to affect performance

The optimization doesn't require '--allow_natives_syntax'; only the check does.

Check if an object's property access is in optimized mode with optimize.check(). This tries to enable the flag '--allow_natives_syntax', so, use in testing and performance benchmarking. (The flag is required in order to check the optimization status.)

See V8 test

Install

npm install @optimal/object --save

Usage

// 1. optimize a an object
var optimize = require('@optimal/object')

var object = {
  key :'value',
  some:'thing',
  and :'more',
}

// trigger slow mode
delete object.and

// back to fast access
optimize(object)

// 2. test an object to know if it's optimized:
var someOtherObject = getSomeOtherObject()
result = optimize.check(someOtherObject) // returns true or false

Others

  1. @optimal/fn

MIT License