Skip to content

feat: upgrade website to new angular scaffolding #140

@ProgrammingByPermutation

Description

Many of the features of angular upgraded properly with automated upgrades but they didn't exactly move us to the "new stuff."

For example:

  • New angular deployments use vitest instead of karma
    • The upgrade left us on karma without mention of the vitest
  • The upgrade mentioned it failed to move to the new build system
    • This may have been erroneous. The angular.json matched in the important ways for the build
    • The manual upgrade documentation doesn't match the output of a fresh angular project creation (e.g. folder names)
  • New angular deployments use public instead of assets
    • No change when upgrading

I'm sure a whole bunch of other things I don't even know about.

It may be worthwile, since the site has so little content, to create a brand new project with the angular cli and port the pages we actually use over.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions