-
Notifications
You must be signed in to change notification settings - Fork 9
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
Various upgrades #1716
Various upgrades #1716
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
GBPTM Run #1292
Run Properties:
|
Project |
GBPTM
|
Branch Review |
refs/pull/1716/merge
|
Run status |
Passed #1292
|
Run duration | 03m 36s |
Commit |
a668bdbd71 ℹ️: Merge 2dd2f2572bee141f782bdc3ae6397034dc6dd84e into bca22eff82ce92c33eae964683b8...
|
Committer | Oliver Barnwell |
View all properties for this run ↗︎ |
Test results | |
---|---|
Failures |
0
|
Flaky |
0
|
Pending |
0
|
Skipped |
0
|
Passing |
63
|
View all changes introduced in this branch ↗︎ |
2417ea0
to
f39b8e8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd recommend pinning dependencies in package.json
. Also curious about the use of devDependencies
— what do they represent?
yes I agree, has been on my to-do list for a while, I'll raise a followup when I have the time
these have become a bit of a mess over time, some deps for prod are in the dev deps — another followup will be to sort through these and work out which are truly dev deps both followups open to others contributing, let me know if you fancy picking something up! |
What does this change?