Skip to content

Initialize MemDev with a single Plasmo extension project#1

Draft
Aryan0699 with Copilot wants to merge 2 commits into
mainfrom
copilot/initialize-plasmo-project
Draft

Initialize MemDev with a single Plasmo extension project#1
Aryan0699 with Copilot wants to merge 2 commits into
mainfrom
copilot/initialize-plasmo-project

Conversation

Copilot AI commented Jul 13, 2026

Copy link
Copy Markdown

This change bootstraps the repository into one main Plasmo project folder, aligning the repo with the requested extension-first setup. The project now has a runnable/maintainable Plasmo baseline under memdev/.

  • Project scaffold

    • Added a full Plasmo starter app in memdev/ (popup entrypoint, assets, TS config, formatter config, README, and extension workflow files).
    • Established memdev/ as the single main project folder for extension development.
  • Package metadata and dependency correctness

    • Updated extension identity in memdev/package.json to match the repository context (name: "memdev", displayName: "MemDev").
    • Replaced the template-local workspace:* Plasmo dependency with a concrete semver dependency to make installs work in this standalone repository.
  • Resulting repository shape

    • Root remains lightweight (README.md + project folder), with all extension code and config scoped to memdev/.
{
  "name": "memdev",
  "displayName": "MemDev",
  "dependencies": {
    "plasmo": "^0.90.5"
  }
}
Original prompt

With one main project folder , initialize a plasmo project

Copilot AI changed the title [WIP] Initialize Plasmo project within main folder Initialize MemDev with a single Plasmo extension project Jul 13, 2026
Copilot AI requested a review from Aryan0699 July 13, 2026 03:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants