chore(tests): satisfy import/order lint in the new test files

Summary: The test files added by the preceding fixes placed the vi.hoisted(() => { ...document stub... }) block between the vitest import and the source imports (the stub has to run before the runtime barrel — which touches document at module load — executes). vi.hoisted() is hoisted above all imports regardless of where it is written, so its position in the source is purely cosmetic; but sitting between imports tripped import/order (“no empty line between import groups”). A couple of files also had imports out of alphabetical order.

Move every vi.hoisted(...) stub block below the import statements and let eslint --fix normalize the import ordering. Pure test-file housekeeping — no change to what any test does (verified by re-running the suites). This batches the lint cleanup for all the new test files into one commit rather than restacking the 16-commit fix series.

Note: the remaining repo import/order errors in src/** (../ecs/entity.js before ../ecs/system.js, etc.) are pre-existing and untouched here.

Reviewed By: cabanier

Differential Revision: D107601296

fbshipit-source-id: df9ea577443da1fabc5005677d1867cc548b4f13

Immersive Web SDK

Where every webpage can become a world.

The Immersive Web SDK makes building immersive web experiences as approachable as traditional web development. It’s a complete collection of frameworks and tools built on Three.js with a high-performance Entity Component System, developer-first workflow with one-command setup and built-in emulation, and production-ready systems for grab interactions, locomotion, spatial audio, physics, and scene understanding.

Same code, two experiences: Run immersively in VR/AR headsets and automatically provide mouse-and-keyboard emulation on desktop browsers. No browser extensions, no special setup—anyone with a laptop can develop for the immersive web.

Getting Started

Create a new project with a single command:

npm create @iwsdk@latest

Or install into an existing project:

npm install @iwsdk/core three

Documentation

For guides, concepts, and API reference, visit: https://iwsdk.dev

Packages

Package	Description
@iwsdk/core	Core SDK with ECS, systems, and WebXR integration
@iwsdk/create	CLI for scaffolding new projects
@iwsdk/glxf	GLXF scene format loader for Three.js
@iwsdk/locomotor	Locomotion engine for Three.js WebXR
@iwsdk/xr-input	WebXR input system for Three.js
@iwsdk/vite-plugin-dev	XR emulation, AI agent tooling, and dev browser
@iwsdk/vite-plugin-gltf-optimizer	GLTF/GLB optimization during build
@iwsdk/vite-plugin-uikitml	UIKitML to JSON compiler for spatial UI
@iwsdk/vite-plugin-metaspatial	Meta Spatial Editor integration

Internal Packages

Package	Description
@iwsdk/starter-assets	CDN-hosted templates and assets for CLI

Development

# Install dependencies
pnpm install

# Build all packages as tgz files (for examples to consume)
npm run build:tgz

# Run an example (fresh install from local tgz packages)
cd examples/locomotion && npm run fresh:dev

# Lint and format
pnpm run lint
pnpm run format

# Build a specific package
pnpm --filter @iwsdk/core build

Development Workflow

The examples use file: dependencies pointing to .tgz files built from local packages. This simulates how end-users will consume the packages from npm.

npm run build:tgz - Builds all packages in dependency order and creates .tgz archives
npm run fresh:dev (in example) - Cleans node_modules, reinstalls from tgz files, and starts dev server

This ensures examples always test against the latest local build.

License

IWSDK is licensed under the MIT License. See the LICENSE file for details.

Contributing

Contributions are welcome! Please review our Contributing Guidelines and Code of Conduct before submitting issues or pull requests.