Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roadmap #369

Closed
5 of 8 tasks
balloob opened this issue Aug 3, 2017 · 0 comments
Closed
5 of 8 tasks

Roadmap #369

balloob opened this issue Aug 3, 2017 · 0 comments

Comments

@balloob
Copy link
Member

balloob commented Aug 3, 2017

While migrating to polymer-build I came to the conclusion that our build of the frontend is a real mess. We can do better 馃憤

Migrating to polymer-build required some hacks but now that it's in, it will be a good first step to a better future. Here are the following steps:

  • Use polymer-build so that we can use ES2015 (requirement for Polymer 2) - Add build using polymer-build聽#344
  • Upgrade to Polymer 2 - Road to Polymer 2.0聽#308
  • Consolidate all frontend pieces in home-assistant-polymer.
    • Migrate static folder from home-assistant to home-assistant-polymer
    • For PyPi packages, include home-assistant-polymer/build.
    • Generate gzip in gulp task
    • Generate version MD5 hashes in gulp task and store in versions.json in build/. Update frontend.py to read versions from there.

Side tasks for the frontend:

  • Migrate hass.io panel gulp task from vulcanize to polymer-build
  • Migrate gen-service-worker gulp task to be a real gulp task, fix minifying the code?
  • Start migrating components to extend Polymer.Element (depends on Polymer 2, requires Hass.io being migrated)
  • Migrate from deprecated paper-drawer-panel to use app-layout https://github.com/PolymerElements/paper-drawer-panel
  • Use external babel-helpers for bundle.

When the migration of hass.io panel to polymer-build is done, we can start using ES2015 in our web components. We cannot use it before that because the hass.io panel build script uses Vulcanize which is not ES2015 compatible.

@balloob balloob closed this as completed Feb 26, 2018
tkdrob pushed a commit to tkdrob/frontend that referenced this issue Apr 20, 2021
Bumps [react-dom](https://github.com/facebook/react/tree/HEAD/packages/react-dom) from 16.13.1 to 16.14.0.
- [Release notes](https://github.com/facebook/react/releases)
- [Changelog](https://github.com/facebook/react/blob/master/CHANGELOG.md)
- [Commits](https://github.com/facebook/react/commits/v16.14.0/packages/react-dom)

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@github-actions github-actions bot locked and limited conversation to collaborators Jul 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant