Unable to use chrome 143 version

[galetahub]

Hi @blakebyrnes,

Thank you for all the great work on Hero! Would it be possible to publish a new release soon?
There have been some updates (browser-emulator-builder) merged since the last one, and having an official release would make it much easier to use them in our projects.

Thanks again for maintaining this project 🙏

• can update 140 chrome? #381

[blakebyrnes]

I unfortunately don't have the time to do releases at the moment. You can run npx @ulixee/default-browser-emulator update-unblocked-emulators to upload the latest browser emulator builder data.

To make this process a little easier for you, I'd like to start publishing the emulator data separately from the hero releases. That would mean you could just update them to get the latest. Steps look something like:

1. Create a new package (@ulixee/unblocked-browser-emulator-data) inside browser-emulator-builder/data. Add this to the workspace. These should have some kind of semver based on a date, probably breaking for each version since they'll be largely untested.
2. In default-browser-emulator, link to this package, but allow greater versions (maybe *? or a peer dependency and force the user to choose the version?).
3. Update the default browser emulator to resolve files out of the emulator instead of copying them into the project (basically need to look for the places that are copying the data folder into here)
4. Change the workspaces/emulator-data.yml to increment the version of this new package and publish it.

If anyone wants to help out, those are the sub-issues of this issue.