Skip to content
This repository was archived by the owner on Oct 13, 2024. It is now read-only.

Story - Support Angular#47

Draft
samhuk wants to merge 1 commit into
masterfrom
story/v3
Draft

Story - Support Angular#47
samhuk wants to merge 1 commit into
masterfrom
story/v3

Conversation

@samhuk

@samhuk samhuk commented Mar 31, 2023

Copy link
Copy Markdown
Owner

Aim

This PR aims to:

  • Serve as an investigation into supporting Angular (work required, etc.)
  • "landing ground" for any progress towards it.

Progress so far

So far, this PR creates an Angular Component Site PoC, without rootStyles or component props support. It can be ran by npm run build-comp-site-angular-build && npm run watch-comp-site-angular-dev.

Investigation Conclusions

  • The index.exh.ts file is included as usual just like it is for the React Component Site. This appeared to work as expected. No problems surfaced here.
  • Several aspects about the Component Site codebase that are problematic, most of which stem from the fact that it is tailored towards React and React-like frameworks.
  • Angular is a very heavy and fat framework that is highly controlled - very different from React.
    • With React:
      • Can just be built by esbuild into a bunch HTML, CSS, and JS.
      • Then served by Site Server.
      • Therefore easy integration with rest of Exhibitor, e.g. Intercom
    • With Angular:
      • Angular apps require a very precisely set up directory with framework config files.
      • Requires the Angular CLI to serve all of the files.
      • Therefore difficult to integrate with Intercom.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant