PlasmoHQ / plasmo

🧩 The Browser Extension Framework
https://www.plasmo.com
MIT License
10.59k stars 369 forks source link

[RFC] plasmo package should accept file name #1073

Open muzammil0011 opened 2 months ago

muzammil0011 commented 2 months ago

How do you envision this feature/change to look/work like?

The framework should get zip file name as optional. If the user provides filename the zip file should be created with that file name. Or by default instead of creating chrome-mv3-prod.zip, the file name should be the name key from package.json with version name included.

Like this is my package.json:

{
  "name": "test-extension",
  "version": "1.0.0"
}

The pnpm package should create a zip file like test-extension-v1.0.0.zip instead of chrome-mv3-prod.zip.

Two command formats:

pnpm package should generate test-extension-v1.0.0.zip pnpm package "Extension-Name" should generate Extension-Name-v1.0.0.zip

Also, pnpm package should first run pnpm build by default so we dont have to run 2 commands.

There should also be a command to increase version like "pnpm updateVersion" so that we don't have to touch package.json for updating version.

What is the purpose of this change/feature? Why?

The purpose of this feature is to provide ease and save developers time. Because packaging extension and then renaming is a big headache 😒

(OPTIONAL) Example implementations

No response

(OPTIONAL) Contribution

Verify canary release

Code of Conduct