-
Notifications
You must be signed in to change notification settings - Fork 68
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
chore: upgrades minor and patch deps #420
Conversation
@@ -0,0 +1,3 @@ | |||
{ | |||
"typescript.tsdk": "node_modules/typescript/lib" |
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.
Nice, we configured it here. I had similar one in my user settings.
@@ -31,14 +31,14 @@ | |||
"version-nightly": "bash scripts/should-nightly-run.sh && npm version prerelease --no-git-tag-version --preid=$(git rev-parse HEAD)", | |||
"postversion": "bash scripts/push-if-git.sh", | |||
"bundlesize": "yarn build && yarn build:dead-code-elimination && size-limit", | |||
"postinstall": "npx yarn-deduplicate" | |||
"postinstall": "npx yarn-deduplicate && yarn --ignore-scripts" |
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.
Are we ignoring postinstall script for dependencies? Any specific reason? 🤔
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.
only for postinstall - this is to stabalize the yarn lock after de-duping (and so it doesnt result in an infinite loop)
unfortunately there can be instances where running yarn after yarn de-dupe will result in the yarn lock file updating again
t.variableDeclaration('const', [t.variableDeclarator(sheetIdentifier, t.stringLiteral(sheet))]) | ||
); | ||
const parent = meta.parentPath.findParent((path) => path.isProgram()); | ||
const parentBody = parent && (parent.get('body') as NodePath[]); |
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.
So all of these started breaking just after patch/minor bump ups? 😨
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.
yeah
@@ -21,11 +23,14 @@ export const getImportDeclarationCollection = ({ | |||
j: JSCodeshift; | |||
collection: Collection<any>; | |||
importPath: string; | |||
}) => | |||
collection | |||
}): Collection<ImportDeclaration> => { |
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.
Love explicit typings over implicit one. TS compiler will be fast if we specify return types.
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.
we could add an eslint rule for that too.
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.
Maybe later. Should we add card for this? Because it might require changes too.
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.
added #422
86702fd
to
5562175
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.
lgtm
This actually shows the type errors we saw when doing your interpolation changes @pgmanutd.
This is a pre-req for the
runtime: automatic
jsx fix.