Migrate to Live Preview

[digitarald]

We are planning to migrate from this extension to Live Preview.

The main reasons are that @auchenberg doesn't have time for maintenance and that many of the features covered in this extension like in-editor preview and debugging are provided by Live Preview (also thanks to new support for webviews that wasn't available when Browser Preview came out).

Goal: Deprecate Browser Preview and help new and existing users to move to Live Preview.

Non-goals:

• Long-term maintenance of Browser Preview.
• Migrate large architecture features like Headless-Chromium-based preview to Live Preview, as we want to invest in a webview and browser-based preview.

Scope:

• [x] Update readme. Depreciation warning and point to new Live Preview.
• [ ] Update package title and description. Adding [Deprecated].
• [ ] Notify existing users. Trigger a notification on activation that explains the deprecation and lets users migrate to Live Preview.
• [ ] Avoid extension conflicts. Disable or prevent activation of Browser Preview when Live Preview is installed, so they don't conflict.

Considerations, based on user feedback:

• Migrate browser preview settings.
• Prioritize any feature gaps for Live Preview to make migration easier.

[Enteleform]

@digitarald

Considerations, based on user feedback:

• Migrate browser preview settings.
• Prioritize any feature gaps for Live Preview to make migration easier.

Do you have any ideas of what the second point entails so far?

 
I switched to Browser Preview because I'm using some ESNext features that were not working with the built-in Simple Browser. I was able to resolve this by utilizing the chromeExecutable setting with MS Edge.

 
After you pointed me to the deprecation notice, I checked out Live Preview, but immediately found that it would not work for my use case at the beginning of their readme:

Note: this extension is intended for projects where a server is not already created (e.g. not for apps using React, Angular, etc.).

 
So I guess I'm wondering if the following things will be addressed in the migration:

• allow custom browser executables
• allow usage w/ existing servers