-
-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat/migrate to new package process #1170
Feat/migrate to new package process #1170
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@niktek let's discuss this during the team meeting today! |
@niktek sorry I haven't been on in the evenings as much to catch you on this, but let me know what's needed here to move this forward. If you set out a set of testing conditions I'll run through that tomorrow. Thanks! |
@niktek I aimed to run the I'm also seeing a ton of uncommitted files after running |
@niktek Both Dom and myself were able to test this and confirm things appear to be working as expected, so I'm going to go ahead and merge. That said, let's monitor this over the next couple weeks, even through release to ensure all is well with the new updates. |
What does your PR address?
Updates to package.json to match new process from SK
Added keywords to show up on npmjs.org
Adjusted pre/post build scripts to reflect new package process
Added quick fixes to A11y warnings so that people might be incentivised to actually test the packageDependencies upgrade - have hard pinned TypeScript to 4.9.5 till it is safe to go to 5.x
Fixes #1163