Builds: Add deprecation warning to build/three.js and build/three.min.js.
#25465
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related issue: #25435 (comment)
Description
Like suggested in #25435 (comment), this PR adds a deprecation warning to
build/three.jsandbuild/three.min.js.Right now, the warning mentioned r160 is the release where the builds are going to be removed and guides towards the Installation guide for alternatives setups.
I'm not sure we want to recommend the
window.THREE = THREE;pattern since it is somewhat a hack. Ideally, users decide for an ESM workflow or a build tool.