MetaMask / MetaMask/metamask-extension

[Bug]: Lavamoat Policy, NPM Package

Open
#37,095 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

external-contributor regression-prod-* Sev2-normal team-lavamoat type-bug
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

### Describe the bug

Hi Team,

I created a new package in which I changed the package name and theme colors. After adding it, where else do I need to make changes like in the Lavamoat policies and other files?

In which files do I need to add it?

If anyone knows about it, please let me know. Thanks

### Expected behavior

_No response_

### Screenshots/Recordings

_No response_

### Steps to reproduce

Add the new package xd-design-tokens
replace the @metamask/design-tokens to xd-design-tokens
make the production build

### Error messages or log output

```shell

```

### Detection stage

In production (default)

### Version

13

### Build type

None

### Browser

Chrome

### Operating system

Linux

### Hardware wallet

_No response_

### Additional context

_No response_

### Severity

_No response_

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 by locating references to @metamask/design-tokens, the Lavamoat policies, and the production build configuration. Reproduce the production build after replacing the package with xd-design-tokens, then identify every required package or policy update. Done means the renamed package builds successfully with its policies updated.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
build-system, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 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.