
Security News
Node.js Drops Bug Bounty Rewards After Funding Dries Up
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.
@jacobtipp/state
Advanced tools
@jacobtipp/state is a Typescript library for creating immutable classes using immer
npm install @jacobtipp/state
Imagine we have a todo application, where a todo item may be fetched from the server,
we can define our state for a todo item by extending the BaseState class like so:
import { BaseState } from '@jacobtipp/state';
type TodoItemStatus = "initial" | "loading" | "ready" | "failed"
class TodoItemState extends BaseState {
constructor(
public id: number,
public message: string,
public status: TodoItemStatus) {
super()
}
}
const todoState = new TodoItemState(0, "", "initial")
// our todoState is initialized but has an empty message, we can set the status to loading while we fetch data from the server
const loadingState = todoState.copyWith((state) => {
state.status = "loading"
})
loadingState !== todoState // true
loadingState.status === "loading" // true
// after the todo item has been fetched we can now update our state with the message
const readyState = loadingState.copyWith((state) => {
state.status = "ready"
state.message = "some message"
})
Defining finite status types is a common practice when dealing with async data, by extending
the State<Data> class, we get utility methods and a constructor that makes this easier
Here we will extend State using the todo item example above:
import { BaseState } from '@jacobtipp/state';
type TodoItem = {
id: number
message: string
}
class TodoItemState extends State<TodoItem> {}
const todoState = new TodoItemState({ id: 0, message: ""})
// the State class automatically provides us with a status property that may have the following values: "initial" | "loading" | "ready" | "failed"
// newly instantiated state objects have an "initial" state by default
todoState.status === "initial" // true
// data is accessed by the "data" property, in this case our TodoItem data
todoState.data.id === 0 // true
todoState.data.message === "" // true
// transitioning between different statuses, we can use the following factory methods: "loading()" | "ready(data: Data)" | "failed(error?: Error)"
const loadingState = todoState.loading()
loadingState.status === "loading" // true
const readyState = loadingState.ready((todoItem) => {
todoItem.message = "some message"
})
readyState.status === "ready" // true
// you can also use the copyWith method, as State inherits from BaseState
const failedState = readyState.copyWith((state) => {
state.status = "failed"
state.error = new TodoItemError()
})
FAQs
## Introduction
We found that @jacobtipp/state demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.

Security News
The Axios compromise shows how time-dependent dependency resolution makes exposure harder to detect and contain.

Research
A supply chain attack on Axios introduced a malicious dependency, plain-crypto-js@4.2.1, published minutes earlier and absent from the project’s GitHub releases.