• Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • None
    • None

      Solution

      The EE webpack config builds on top of the CE webpack config. The code reads the CE config first, adds additional entries on top of that and adjusts a few paths then proceeds with a regular build.

      • pros:
        • EE config is very thin
        • CE changes are automatically picked up in EE
      • cons:
        • CE changes could break the EE webpack as well

      TODOs

      • fix all the places where we load resources by url
        • look for these: templateUrl:, url:, .attr('cockpit-api')
        • use require instead
        • clean up imports
      • make maven build work with webpack
        • call npx webpack instead of grunt
      • clean up webpack config
        • instead of adding EE plugins in CE config, pass EE plugins from EE config to CE config via args
        • CE shouldn't know about EE plugins
      • test (this list is probably incomplete)

        This is the controller panel for Smart Panels app

              daniel.kelemen Daniel Kelemen
              tassilo.weidner Tassilo Weidner
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: