Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFC] plasmo package should accept file name #1073

Open
3 of 4 tasks
muzammil0011 opened this issue Sep 14, 2024 · 0 comments
Open
3 of 4 tasks

[RFC] plasmo package should accept file name #1073

muzammil0011 opened this issue Sep 14, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@muzammil0011
Copy link

muzammil0011 commented Sep 14, 2024

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

  • I would like to contribute to this RFC via a PR

Verify canary release

  • I verified that the issue exists in plasmo canary release

Code of Conduct

  • I agree to follow this project's Code of Conduct
  • I checked the current issues for duplicate problems.
@muzammil0011 muzammil0011 added the enhancement New feature or request label Sep 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant