parcel-bundler
Document changing the webextension manifest name
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| website | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Oct 11, 2023 8:16am |
![vercel[bot] avatar](https://avatars.githubusercontent.com/in/8329?v=4 "Published by a pub.dev verified publisher"){kind=small}
Seems fine for now, however, actual flexibility of having any file name for the manifest will be very much helpful in future.
Turns out this actually doesn't work yet because of this hardcoded name check: https://github.com/parcel-bundler/parcel/blob/c3bbe0a6160186f496ca2f9e9bead9376c0522f1/packages/runtimes/webextension/src/WebExtensionRuntime.js#L18 We'll have to change that to just rely on some asset meta property...
Exactly, that will be great.
On 11/12/2022 3:04 PM, Niklas Mischkulnig wrote:
Turns out this actually doesn't work yet because of this hardcoded name check: https://github.com/parcel-bundler/parcel/blob/c3bbe0a6160186f496ca2f9e9bead9376c0522f1/packages/runtimes/webextension/src/WebExtensionRuntime.js#L18 We'll have to change that to just rely on some asset meta property...
— Reply to this email directly, view it on GitHub https://github.com/parcel-bundler/website/pull/1052#issuecomment-1312425002, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABQWBM6E2KZXWOGS6TIRJ73WH5QB7ANCNFSM6AAAAAARUG5YII. You are receiving this because you commented.Message ID: @.***>
If you stop hard-coding and rely on meta property, the build will go through. However, since the output file name remains the same, it cannot be loaded as a browser extension. I want to convert the file name to manifest.json when outputting, but I can't think of a good way to do it...😞. Do you have any good ideas?
