Skip to content

Conversation

@nthurow
Copy link
Contributor

@nthurow nthurow commented Apr 3, 2024

Proposed changes

Without these fields, applications which use certain legacy TypeScript settings (such as "moduleResolution": "node") were not able to detect the type definitions for @optum/react-core.

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

  • Bugfix (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)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • I have read the CONTRIBUTING doc
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in downstream modules

…ions

Without these fields, applications which use certain legacy TypeScript
settings (such as `"moduleResolution": "node"`) were not able to detect
the type definitions for `@optum/react-core`.
@NielsJPeschel NielsJPeschel merged commit 912b6f5 into main Apr 3, 2024
@NielsJPeschel NielsJPeschel deleted the add_main_types branch April 3, 2024 22:00
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.

3 participants