You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How do you envision this feature/change to look/work like?
Similar to the GitHub action, would be great to be able to specific a custom path to the package.json where the designed version number is located. Something like this:
plasmo build --version-file ../../package.json
What is the purpose of this change/feature? Why?
In monorepos, the source of truth for the app's version is often kept in the root package.json as opposed to in the extension's directory.
(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
How do you envision this feature/change to look/work like?
Similar to the GitHub action, would be great to be able to specific a custom path to the package.json where the designed version number is located. Something like this:
plasmo build --version-file ../../package.json
What is the purpose of this change/feature? Why?
In monorepos, the source of truth for the app's version is often kept in the root package.json as opposed to in the extension's directory.
(OPTIONAL) Example implementations
No response
(OPTIONAL) Contribution
Verify canary release
plasmo
canary releaseCode of Conduct
The text was updated successfully, but these errors were encountered: