-
Notifications
You must be signed in to change notification settings - Fork 60
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
remove glob dependency #701
Conversation
👋 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 |
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'm okay either way, I think the code was easier to grasp using glob
. Is there a particular reason why you would want to remove it? It's just a dev dependency anyway
// Remove the types file from the dist-src folder | ||
const typeFiles = await glob([ | ||
"./pkg/dist-src/**/types.js.map", | ||
"./pkg/dist-src/**/types.js", | ||
]); | ||
for (const typeFile of typeFiles) { | ||
await rm(typeFile); | ||
} | ||
|
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.
Why was this removed? Whenever we have a types.ts
file it would create an empty types.js
file which is useless
There is no types.ts file. |
we dont need glob ;)