-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
Typescript migration #534
Typescript migration #534
Conversation
Uninstalled eslint ✅ Closes: 501
The danger.js package is uninstalled from the project along with its related config files. .travis.yml is deleted. BREAKING CHANGE: 🧨 N/A ✅ Closes: 493
Actually i'm having issues working through tsconfigs right now to make sure we can use update-notifier, it got bumped 4 major versions in one of these PRs lol, and getting esm vs cjs errors atm |
@jwu910 any details/steps to reproduce? I'd be happy to take a look if that would be helpful. |
Hey @drewbrokke, that would be amazing. So far i've seen this issue:
running I'm thinking it has something to do with the module type and/or compile target for TS. but haven't had a chance to really dig in and research it |
These commits (esm:) convert the project to support ESM following this guide: https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c
…calls to require() and __dirname
…ion for development
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.
Lol @drewbrokke just vscode extension Document This, i haven't found a way to automate this based off type annotations yet though, I know there are tools that can generate docs from jsdoc strings, just wanted to keep it uniform where i could |
Description
Fixes #492
Seems like everything was migrated... need to test and double check all the dep updates that went in while this was split prior to cutting a new release (or look into any other features/fixes)
Types of changes
Checklist: