Nathan Fritz

In fact ape should catch things like that whenever an id, component, or entity is passed.

Docs don't indicate that methods can use types directly

2

Documentation needs to be updated to show that methods that type a type-name string can also take the type constructor itself, directly.

If you're writing a Component in TS, you essentially have to define each property twice. Internally, ES class properties use Object.defineProperty every time the class is initialized, which is slow....

"My use case for many-to-many relationships is tracking, say, visibility between multiple entities. There's a bunch of entities with Sight and a partially overlapping set with Presence, and I want...

Currently queries can trackAdded, trackRemoved. We could also have trackChanged, trackChangedValues, trackChangedComponents.

Docs clarification: Query fromAny vs only

1

from* methods only add results to the query, while "not" and "only" filter only remove results that were added by from* methods.

Clarify what that object is, how it is defined, and how property constructors work.

feat: rootless workspace init provides suggestion

2

Adds a warning message suggesting the use of `--include-workspace-root` when ENOENT is thrown for the `npm init` command when specifying one or more workspaces.

feat: deprecate some access subcommands

2

Added warning logs for `npm access ` for the following subcommands: - 2fa-required - 2fa-not-required - public - restricted - edit - ls-packages - ls-collaborators

## THIS PR HAS BEEN MIGRATED Originally from https://github.com/npm/arborist/pull/342 Originally By @ylemkimon This PR adds the ability to add a hook via `options.hook`. It adds a single hook `options.hook[Symbol.for('beforeReify')](Arborist)`, that...