Update dev dependencies and document cleanup#792
Conversation
Document the dev dependency cleanup approach, current warnings, and next steps. Remove temporary audit artifacts from the repo.
Exclude markdown, CSV, and YAML files from coverage collection, and stop treating markdown as Vue SFC input. Escape placeholder brackets in i18n README.
Provide router and store data to render the non-basic view and mock districts query so the dropdown interaction test runs without warnings.
CCuskley
left a comment
There was a problem hiding this comment.
This is a lot to review at once - could we consider breaking this into separate PRs that address updating dev dependencies, removing unused dependencies, and adding documentation in separate PRs? This will allow us to review/test incrementally. Note it's also not passing existing tests so not generating a dev link.
|
This was started back in October with the only "code" being changed as package.json and eliminating a couple unused imports. But as it sat around it got farther out of sync with main and rebasing, etc. cluttered it up completely. Now it's not even close to being right. So if someone wants to pick up the theme (basically dump packages we aren't using for development) I think that'd be useful. The PR also includes a script that identifies un-used packages and produces a report. |
|
Ok sounds good - I do think we need to pick this up, but will convert to draft for now and we can use this as a starting point later. |
Summary
Test plan
npm run build:devNext steps
npm run lintandnpm testto validate toolchain upgrades