Open louisgv opened 2 years ago
This would be really helpful when using plasmo within the nx monorepo. The nx monorepo keeps a single package.json at the repo-root to keep packages and versions aligned, along with caching various aspects of the repo.
Having the plasmo manifest overrides living in a different file would allow me to integrate plasmo into an nx monorepo a bit more effectively.
Override entry file paths
Looking forward to this feature. This would also make #356 more flexible, to support any extension the users want.
Would very much like to pull the plasmo-related stuff out of package.json
🙏
package.json
doesn't support code commentsplasmo.config.ts
allows developers to use the chrome.runtime.ManifestV3
type in @types/chrome
for faster error detection. It is also possible to export the type of a custom command to use it in service_worker.
How do you envision this feature/change to look/work like?
Support a typed configuration file, mainly for manifest override, and other cool stuffs (?).
What is the purpose of this change/feature? Why?
Working with the manifest override (or manifest in general) SUCKS BALLS!?
(OPTIONAL) Example implementations
No response
(OPTIONAL) Contact Details
No response
Verify canary release
plasmo
canary releaseCode of Conduct