Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Environment should not use hard coded defaults

Open
  • Is something wrong?
#220 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@marklundin is already working on this.

Since Sep 3, 2025.

Assessment

This issue has not been assessed yet.

Description

chore React

The Environment component contains hardcoded defaults to app.scene properties. This should be more generic as any changes to the engine defaults will require downstream changes. Meaning that adding and removing the component would not return to the initial state. Ideally the defaults could be inferred from the engine directly.

https://github.com/playcanvas/react/blob/777b88c77ef8b4f3318e900c7deff8abafba32e4/packages/lib/src/components/Environment.tsx#L136-L153

Dominant language
TypeScript
Stars
538
Forks
60
Avg merge
12h 28m
Merged PRs (30d)
10

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from playcanvas/react

All issues in playcanvas/react

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.