🌟 Implemented a way for users to define the output entrypoint name #1304
Conversation
Additional changes: - Added author field to manifest - Implemented recursive finding of package.json
✅ Deploy Preview for creative-fairy-df92c4 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
I don't want to add the ability to add hashes to filenames. This is because in my experience, changing filenames between submissions to the Chrome Web Store and Firefox Addon Store results in longer review times and more manual reviews. My guess is that the diff tools they use don't work well with renamed files, so these submissions get flagged more often. As for your other two changes...
Can you open a separate PR for this?
What is the point of this? What's your use-case for not having a package.json in your extension's root directory? |
|
https://developer.chrome.com/docs/extensions/reference/manifest/author Adding the Author field will break a lot of extensions, it MUST match the email of the Google account that published the extension. Even if this doesn't break anything, I don't understand the point of it since the Author field doesn't seem to be displayed anywhere. |
Additional changes:
check #1302