ljharb / ljharb/es-errors

Dependency Dashboard

Open
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
10
Forks
3
PR merge metrics
No merged PRs in 30d

Description

This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
[View this repository on the Mend.io Web Portal](https://developer.mend.io/github/ljharb/es-errors).

## Deprecations / Replacements
> [!WARNING]
The following dependencies are either deprecated or have replacements available.

| Datasource | Package | Replacement PR? |
|------------|------|--------------|
| npm | [aud](https://redirect.github.com/ljharb/aud) | ![Unavailable](https://img.shields.io/badge/unavailable-orange?style=flat-square) |

## Pending Approval

The following branches are pending approval. To create them, click on a checkbox below.

- [ ] [Deps] Update Update all non-major dependencies (`@ljharb/tsconfig`, `evalmd`)
- [ ] [Deps] Update Update `@ljharb/eslint-config` to v22
- [ ] [Deps] Update Update `aud` to v3
- [ ] [Deps] Update Update `eslint` to v10
- [ ] [Deps] Update Update `nyc` to v18
- [ ] [Deps] Update Update actions/checkout action to v7
- [ ] 🔐 **Create all pending approval PRs at once** 🔐

## Detected Dependencies

github-actions (5)

.github/workflows/node-aught.yml (1)

- `ljharb/actions main`

.github/workflows/node-pretest.yml (1)

- `ljharb/actions main`

.github/workflows/node-tens.yml (1)

- `ljharb/actions main`

.github/workflows/rebase.yml (2)

- `actions/checkout v3` → [Updates: `v7`]
- `ljharb/rebase master`

.github/workflows/require-allow-edits.yml (1)

- `ljharb/require-allow-edits main`

npm (1)

package.json (14)

- `@ljharb/eslint-config ^21.1.0` → [Updates: `^22.0.0`]
- `@ljharb/tsconfig ^0.1.1` → [Updates: `^0.3.0`]
- `@types/tape ^5.6.4`
- `aud ^2.0.4` → [Updates: `^3.0.0`]
- `auto-changelog ^2.4.0`
- `eclint ^2.8.1`
- `eslint ^8.8.0` → [Updates: `^10.0.0`]
- `evalmd ^0.0.19` → [Updates: `^0.0.22`]
- `in-publish ^2.0.1`
- `npmignore ^0.3.1`
- `nyc ^10.3.2` → [Updates: `^18.0.0`]
- `safe-publish-latest ^2.0.0`
- `tape ^5.7.5`
- `node >= 0.4`

---

- [ ] Check this box to trigger a request for Renovate to run again on this repository

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Dependency Dashboard documentation, then review package.json and the listed .github/workflows files to understand the pending dependency updates. Select a specific pending approval entry rather than treating the dashboard as one change; done means the corresponding Renovate PR is created and its update is accepted.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, javascript
Domain
devops, tooling
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.