Status page MVC frontend follow-ups
In the interest of efficiency/iteration, I'm noting down some todos that came up during the review of the initial Status Page frontend MR review https://gitlab.com/gitlab-org/status-page-private/-/merge_requests/1
These are things that don't block the initial development but would be good to have in place as we add features / invite more contributors.
Readme:
-
Add instructions on how to build + run prod locally ( yarn prod && npx http-server dist/
)
General:
-
Set up build, test, review, deploy pipelines -
Add a favicon -
Add Sentry integration to catch uncaught errors and surface these to the team (also to dogfood error tracking) -
Support base-urls
Developer ergonomics:
-
Import and use gitlab's eslint / prettier config -
Add webpack alias for root folder, for absolute imports -
consider a pre-commit hook via husky
Tech debt:
-
Add eslint dependency so we don't use the global package (which can cause unexpected issues) -
Add unmet peer dependencies to package.json (will raise visibility on dependency versions and reduce noise of yarn install
command)
Feel free to add more things. Anything that ends up being a large task - we can split off and create a separate issue.
Edited by Tristan Read