Studio: new-project scaffold pins `@rendiv/*` to `^0.1.0`, so Studio 0.2.6 creates projects on core 0.1.20

Open Beginner friendly
  • Is something wrong?
#17 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
node.js, typescript
Domain
tooling

Research direction

Read the inline template in packages/studio/src/scaffold-project.ts and diff it against packages/create-rendiv/src/template/package.json.tmpl, which already carries ^0.2.0. Reproduce by creating a project from the Studio picker and checking node_modules/@rendiv/core/package.json, then decide whether to read the create-rendiv template or substitute Studio's own version at build time. Done when a newly scaffolded project resolves core 0.2.x and the two template copies can no longer drift.

Written by the indexing model from the issue text.

Description

bug

Summary

A project created from the Studio workspace picker is installed on @rendiv/core 0.1.20, even when the Studio that created it is 0.2.6.

Cause

packages/studio/src/scaffold-project.ts keeps its own inline copy of the project template (the comment says "same as create-rendiv"), and its package.json still has:

"@rendiv/core": "^0.1.0",
"@rendiv/player": "^0.1.0",
"@rendiv/cli": "^0.1.0",

A caret on a 0.x version stays inside 0.1.x, so npm resolves these to 0.1.20. packages/create-rendiv/src/template/package.json.tmpl was already moved to ^0.2.0; only the Studio copy was left behind.

Reproduction

  1. Run Studio 0.2.6 in workspace mode and create a project from the picker.
  2. grep '"version"' node_modules/@rendiv/core/package.json in the new project prints 0.1.20.

Suggested fix

Stop keeping two copies of the template: have the Studio scaffold read the create-rendiv template, or fill the @rendiv/* versions in from Studio's own version at build time, so the two cannot drift again.

Dominant language
TypeScript
Stars
159
Forks
32
No merged PRs in 30d

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 thecodacus/rendiv

All issues in thecodacus/rendiv

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.