Skip to content

Docs: custom metro config for three.js appears not to be needed in all environments #408

Description

@nickw1

Following up my previous issue, another thing I noticed is that in my environment (Expo project running Expo 56) I did not need to change my Metro config. The correct WebGPU version of three.js is imported simply by importing three/webgpu.

Not sure if this is the case for all environments, have not tested on any other.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions