-
Notifications
You must be signed in to change notification settings - Fork 89
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
fix tsc errors, and run it in prs too #391
Conversation
}, | ||
"devDependencies": { | ||
"@babel/preset-react": "^7.18.6", | ||
"@babel/preset-typescript": "^7.18.6", | ||
"@linaria/esbuild": "^4.1.4", | ||
"@linaria/shaker": "^4.2.1", | ||
"@types/babel__core": "^7.1.20", |
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.
These were needed since Linaria's types reference them
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 wonder why linaria doesn't have it as a dependency then? I guess types cannot have dependencies
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.
It's always been kind of an annoying thing: you have types that expose stuff from another package, but you also don't want to mark that package as a 'production dependency' since it might not actually be used at runtime and therefore unnecessary for non-TypeScript consumers.
}, | ||
"dependencies": { | ||
"@linaria/react": "^4.1.4", | ||
"@popperjs/core": "^2.11.2", | ||
"@popperjs/core": "^2.11.6", |
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.
2.11.2 had types that failed to compile in TS 4.9
No description provided.