Repository navigation
chore: initialize marketing-consent-controller package - #10859
Open
zelkibuilds wants to merge 2 commits into
Open
zelkibuilds wants to merge 2 commits into
zelkibuilds wants to merge 2 commits into
Conversation
Package scaffold only, generated with create-package: placeholder greeter export, empty changelog, and monorepo registration (CODEOWNERS, teams.json, tsconfig references, yarn.lock). Uses Vitest, as new packages are expected to.
3 of 4 tasks
zelkibuilds
added this pull request to stack #10860
October 16, 2026 10:41
baptiste-marchand
previously approved these changes
Oct 16, 2026
Mrtenz
reviewed
Oct 16, 2026
| same "printed page" as the copyright notice for easier | ||
| identification within third-party archives. | ||
|
|
||
| Copyright [yyyy] [name of copyright owner] |
Member
There was a problem hiding this comment.
Suggested change
| Copyright [yyyy] [name of copyright owner] | |
| Copyright 2026 MetaMask |
Co-authored-by: Maarten Zuidhoorn <maarten@zuidhoorn.com>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Explanation
Scaffold for the new
@metamask/marketing-consent-controllerpackage, split out of #10821 following the two-PR process for new packages. No functional changes.create-package: placeholdergreeterexport, empty changelog, license files, tsconfigs andtypedoc.json.tsconfig.lint.json, whichcreate-packagedoesn't add),CODEOWNERS,codeowners.ts,teams.json(team-engagement) andyarn.lock.create-packagestill generates, since new packages are expected to use Vitest (test: add Vitest alongside Jest #10546):vitest.config.jsextendsvitest.config.packages.js, with 100% coverage thresholds.The implementation is stacked on this branch in #10821.
References
@metamask/marketing-consent-controllerand marketing consent check in NSC #10821Checklist
Note
Low Risk
Monorepo scaffolding and ownership metadata only; no production logic or integration changes.
Overview
Introduces
@metamask/marketing-consent-controlleras a new monorepo package (intended to keep marketing consent in sync with Authenticated User Storage). This PR is scaffolding only: standard package layout, licenses, changelog, TypeDoc/tsconfig build wiring, a placeholdergreeterexport, and a Vitest setup with 100% coverage thresholds (not Jest).The package is registered across the repo—root README, TypeScript project references (including lint),
yarn.lock,CODEOWNERS/codeowners.ts, andteams.jsonmapping it to team-engagement (@MetaMask/engagement). No runtime or consumer-facing behavior ships here; implementation is expected in a follow-up (e.g. #10821).Reviewed by Cursor Bugbot for commit 0e67e15. Bugbot is set up for automated code reviews on this repo. Configure here.