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

Remove types not part of THREE namespace anymore #1981

Merged
merged 2 commits into from
Jan 12, 2022

Conversation

Dig-Doug
Copy link
Contributor

@codesandbox-ci
Copy link

codesandbox-ci bot commented Jan 11, 2022

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit feb66f0:

Sandbox Source
example Configuration

Copy link
Member

@CodyJasonBennett CodyJasonBennett left a comment

Choose a reason for hiding this comment

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

Looks good. @drcmda @joshuaellis, we'll want to send out a patch release but bump the three per dep to r133 where ParametricGeometry, TextGeometry, etc. were removed.

@joshuaellis
Copy link
Member

@drcmda @joshuaellis, we'll want to send out a patch release but bump the three per dep to r133 where ParametricGeometry, TextGeometry, etc. were removed.

I agree, probably best to bump the peer dep in this PR?

@Dig-Doug
Copy link
Contributor Author

I've updated the three and @types/three versions to "^0.133.0".

@CodyJasonBennett CodyJasonBennett merged commit e5ec292 into pmndrs:master Jan 12, 2022
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.

Build issue: Expression produces a union type that is too complex to represent
3 participants