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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@a11d/is-writable

v1.0.2

Published

A function on the Object constructor that determines if a property is writable.

Readme

@a11d/is-writable

Check if an object property is writable, accounting for property descriptors, getters/setters, and the prototype chain.

import '@a11d/is-writable'

const obj = { name: 'John' }
Object.defineProperty(obj, 'id', { value: 123, writable: false })

Object.isWritable(obj, 'name') // true
Object.isWritable(obj, 'id') // false

Installation

npm install @a11d/is-writable

API

Returns true if the property is writable, false otherwise.

const obj = {}
Object.defineProperty(obj, 'readonly', { value: 42, writable: false })

Object.isWritable(obj, 'readonly') // false
Object.isWritable(obj, 'newProp') // true (non-existent properties are writable)

Checks the entire prototype chain:

class Base {
	get value() { return 1 }
}

class Child extends Base {}

Object.isWritable(new Child(), 'value') // false (getter-only in prototype)

Behavior

Returns false for all properties on frozen objects:

const obj = { name: 'John' }
Object.freeze(obj)

Object.isWritable(obj, 'name') // false
Object.isWritable(obj, 'newProp') // false

Getter-only properties are not writable:

const obj = {
	get value() { return 42 }
}

Object.isWritable(obj, 'value') // false

Properties with both getter and setter are writable:

const obj = {
	get value() { return this._value },
	set value(v) { this._value = v }
}

Object.isWritable(obj, 'value') // true

Setter-only properties are writable:

const obj = {
	set value(v) { console.log(v) }
}

Object.isWritable(obj, 'value') // true

Properties that don't exist are considered writable (unless the object is frozen):

const obj = {}
Object.isWritable(obj, 'newProp') // true

Checks all descriptors in the prototype chain:

class Base {
	get value() { return 1 }
}

class Child extends Base {
	get value() { return 2 }
	set value(v) { /* add setter alongside getter */ }
}

Object.isWritable(new Base(), 'value') // false (getter-only)
Object.isWritable(new Child(), 'value') // true (has both getter and setter)