-
Notifications
You must be signed in to change notification settings - Fork 0
Open
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.jsonmatched 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)
- This may have been erroneous. The
- New angular deployments use
publicinstead ofassets- 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
Labels
No labels
Type
Projects
Status
Backlog