Skip to content
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

Merged
merged 53 commits into from
Jul 13, 2023
Merged

Typescript migration #534

merged 53 commits into from
Jul 13, 2023

Conversation

jwu910
Copy link
Owner

@jwu910 jwu910 commented Jun 20, 2023

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

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update

Checklist:

  • I have read the CONTRIBUTING document.
  • My commits follow the commitizen commit convention
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

jwu910 and others added 29 commits February 20, 2023 16:56
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
@jwu910 jwu910 requested a review from kienD as a code owner June 20, 2023 04:22
@jwu910
Copy link
Owner Author

jwu910 commented Jun 20, 2023

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

@drewbrokke
Copy link
Collaborator

@jwu910 any details/steps to reproduce? I'd be happy to take a look if that would be helpful.

@jwu910
Copy link
Owner Author

jwu910 commented Jul 11, 2023

Hey @drewbrokke, that would be amazing.

So far i've seen this issue:

  1. npm run build (on latest typescript-migration branch
  2. npm link
  3. cio

running node dist/index.js after the build is also throwing the error.

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

@drewbrokke
Copy link
Collaborator

@jwu910 see #535.

@jwu910
Copy link
Owner Author

jwu910 commented Jul 13, 2023

@jwu910 see #535.

I think we're good to merge 😂 if you get a minute tomorrow, would you be able to take another pass over the changes? not sure what else we need to do, either than maybe config clean up from some of the templated files. maybe some doc updates before any release, too

Copy link
Collaborator

@drewbrokke drewbrokke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM @jwu910 👍

Did you use tooling to accomplish 41cc6e1? If so, is it integrated into an npm script?

@jwu910
Copy link
Owner Author

jwu910 commented Jul 13, 2023

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

@jwu910 jwu910 merged commit be1a258 into main Jul 13, 2023
4 checks passed
@jwu910 jwu910 deleted the typescript-migration branch July 13, 2023 14:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feat: Upgrade to TS ➕ 🦖
4 participants