panel_custom: Allow ES5+latest build, deprecate html

[balloob]

Breaking change

Specifying custom panels based on HTML imports is being deprecated and will be removed in a future version.

Proposed change

Allow specifying both an es5 + latest build for custom panels.

Deprecates specifying HTML panels.

Requires home-assistant/frontend#6104

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

[mkarnebeek]

Can I ask a question? I'm using panel_custom: for https://gist.github.com/AdamNaj/cbf4d792a22f443fe9d354e4dca4de00 -- Is there a replacement

Also https://www.home-assistant.io/integrations/panel_custom/ doesn't say anything about it being deprecated

I'm using it as:

panel_custom:
  - name: zwavegraph2
    sidebar_title: Z-Wave Graph
    sidebar_icon: mdi:access-point-network
    url_path: zwave_graph

And as far as I know i'm not using anything which is deprecated

[Mariusthvdb]

yes, please let us know, because there is some confusion on the way forward, a least for this. See https://community.home-assistant.io/t/z-wave-graph-without-the-python/64275/349

[balloob]

That integration needs to be rewritten to use JS as the entrypoint, not HTML.

[nickrout]

Why is this needed? Deprecation doesn't fix any issue (according to the above)

[balloob]

HTML imports was a draft spec that was not accepted by the browsers. Only Chrome had it implemented and has since removed it. It requires Home Assistant to include extra logic and code to keep supporting it. If someone can write an HTML panel, they can write a JS panel.

[nickrout]

Thank you :)