-
Notifications
You must be signed in to change notification settings - Fork 14
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: update to current best practices #394
base: main
Are you sure you want to change the base?
Conversation
- Update esbuild to output ESM - Remove jest in favour of vitest - Don't add `@types/node` in the devDependencies to avoid having it leak into the outputted types
👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with |
test: { | ||
coverage: { | ||
include: ["src/**/*.ts"], | ||
exclude: ["src/methods/get-oauth-client-code.ts"], // Exclude this file from coverage as it isn't exported |
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.
Do we need this?
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.
Nope
@@ -3,14 +3,14 @@ export { createEsbuildScript }; | |||
import { writePrettyFile } from "./write-pretty-file.js"; | |||
|
|||
async function createEsbuildScript(answers) { | |||
const nodeBuildOptions = ` // Build a CJS Node.js bundle | |||
const nodeBuildOptions = ` // Build an ESM Node.js bundle |
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 feel we are at a point where we should test the output of running this script is the expected one. Do you think it's worth investing in this?
@types/node
in the devDependencies to avoid having it leak into the outputted typesResolves #ISSUE_NUMBER
Before the change?
After the change?
Pull request checklist
Does this introduce a breaking change?
Please see our docs on breaking changes to help!