JSPM

three-stdlib

0.0.13
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 442027
  • Score
    100M100P100Q172087F
  • License MIT

Package Exports

  • three-stdlib
  • three-stdlib/controls/DeviceOrientationControls
  • three-stdlib/controls/FlyControls
  • three-stdlib/controls/OrbitControls
  • three-stdlib/controls/PointerLockControls
  • three-stdlib/controls/TrackballControls
  • three-stdlib/controls/TransformControls
  • three-stdlib/lines/Line2
  • three-stdlib/lines/LineGeometry
  • three-stdlib/lines/LineMaterial
  • three-stdlib/loaders/DRACOLoader
  • three-stdlib/loaders/FBXLoader
  • three-stdlib/loaders/GLTFLoader
  • three-stdlib/loaders/RGBELoader
  • three-stdlib/math/SimplexNoise
  • three-stdlib/modifiers/CurveModifier
  • three-stdlib/modifiers/EdgeSplitModifier
  • three-stdlib/modifiers/SimplifyModifier
  • three-stdlib/modifiers/TessellateModifier
  • three-stdlib/objects/Sky
  • three-stdlib/postprocessing/EffectComposer
  • three-stdlib/postprocessing/RenderPass
  • three-stdlib/postprocessing/ShaderPass
  • three-stdlib/shaders/GammaCorrectionShader
  • three-stdlib/shaders/HorizontalBlurShader
  • three-stdlib/shaders/VerticalBlurShader

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (three-stdlib) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

npm install three-stdlib
// Export collection
import * as STDLIB from 'three-stdlib'
// Flatbundle
import { OrbitControls, ... } from 'three-stdlib'
// Pick individual objects
import { OrbitControls } from 'three-stdlib/controls/OrbitControls'

This is a stand-alone of https://github.com/mrdoob/three.js/tree/dev/examples/jsm

Our main goals are:

  • Real, npm/node conform esm modules with marked dependencies
  • Class based, optimized for tree-shaking, no global pollution, exports instead of collections
  • A build system for esm and cjs
  • Single flatbundle as well as individual transpiles
  • Typesafety with simple annotation-like types
  • CI, tests, linting, formatting (prettier)

But most importantly, allowing the people that use and rely on these primitives to hold a little stake, and to distribute the weight of maintaining it. Jsm/examples were always considered as something that you copy/paste into your project and adapt to your needs. But that is not how people use it.

Let's give jsm/examples the care it deserves!

Changes

  • All Collections have been converted to export maps (GeometryUtils, CurveExtras, etc)
  • WebGL has been moved to /misc