Publish @demo packages
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 122
- Forks
- 29
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 2
Description
import { Scene as Aquarium } from "@demo/aquarium"
import { Scene as BasicDemo } from "@demo/basic-demo"
function App() {
return (
<Canvas>
// do something with Aquarium, BasicDemo like <Route>s
</Canvas>
)
}
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Review the monorepo's package layout and existing publishing configuration, then determine how @demo/aquarium and @demo/basic-demo should be published so the imports shown in the issue resolve.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100