-
Notifications
You must be signed in to change notification settings - Fork 897
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
Enable changesets #3268
Enable changesets #3268
Conversation
Binary Size ReportAffected SDKs
Test Logs |
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.
Looks good! I had one question but just asking for my knowledge.
return packagePaths | ||
.map(path => { | ||
try { | ||
return require(`${path}/package.json`); | ||
return JSON.parse(readFileSync(`${path}/package.json`, 'utf8')); |
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.
Just out of curiosity is it because ts-node can't require json files?
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.
require
caches the content of the package.json, so you will read stale package.json
if you read it first, update it, then read it again. using readFile
will always get the latest version from disk.
Once merged, we will need to install the changeset Github App.