haterapps
commented
2 years ago Update on the new Fake Data migration to MV3:
You can install a BETA version for Fake Data from this link (Chrome only for now): https://chrome.google.com/webstore/detail/fake-data-beta/cgdofifkggagondhlalkbfpdgneifkkk
Read more details about how the MV3 will work under the hood and what changes you will need to make in your code: https://docs.fakedata.pro/writing-code/mv2-to-mv3-migration.html
Keep in mind that the beta version is a completely separate extension. Do not uninstall your current stable version because you will lose your data. You can temporarily disable the stable extension, so you don't have 2 versions at the same time, and you can quickly resume using it without losing anything.
There are still many things to do and multiple features that are somehow broken in this beta version. You can post here any problems that you find (either in this thread or create a new issue) so I can fix them in the next beta release.
allanlaal
EpicVoyage
UPDATED 2024-05-24
Starting with version 4.9.0, the Chrome build will be released with MV3. If you're having any issues with your custom codes, please report them.
UPDATED 2022-03-29
Read more details about MV3 migration and how it will work on the following link: https://docs.fakedata.pro/writing-code/mv2-to-mv3-migration.html
Install the BETA version of Fake Data that runs on MV3 and help identify issues or bugs in your workflow earlier: https://chrome.google.com/webstore/detail/fake-data-beta/cgdofifkggagondhlalkbfpdgneifkkk
Important changes are coming!
Starting with January 2023 Google will require all Chrome extensions to be released with their new API, called MV3 (Manifest version 3). This will be a requirement for all extensions in the web store as well as the ones that are sideloaded, otherwise they will stop working in latest versions of the browser.
You can see more about the timeline here.
What does this mean for Fake Data?
Because the transition from MV2 to MV3 is big and with significant changes, a lot of the code will be rewritten and adapted for the changes that are coming, so we can all be able to continue using Fake Data as before.
What does this mean for users?
One of the huge breaking changes that MV3 brings is that extensions can no longer execute remote code as easily as before. While this may sound good in theory and will stop malicious extensions to execute code that is not bundled within them, it will also prevent legit uses of remote code.
Unfortunately, for Google, "remote code" does not mean only the code is downloaded from a remote server and then executed by the extension. It also means any code that is not bundled with the package.
In Fake Data's case, it means that features like "Custom Generators", "fields with Custom Code", "Before and After callbacks", and "Loaded Libraries" will stop working as it's considered "remote hosted code".
But there is still hope. While MV3 restricts executing custom javascript code within its context, it still allows it to run in a sandboxed page that doesn't have access to any of the APIs or access to the DOM elements of the page you are in.
While I will do my best to make the transition as smooth as possible, with the best workarounds I can, there might be cases where the custom code you are using will need to be rewritten and adapted.
What should you expect next?
Conclusion
Since these changes are big and will need a lot of work, there will be less updates to Fake Data in the first months of this year, unless there are breaking issues or very small fixes.
In order to be kept updated with this, the best way would be to subscribe to this thread so you will receive updates as they will be posted.
Thank you for understanding!