posit-dev / posit-dev/shinyreact
feat: secondary pkgs should vendor their JS
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 14
- Forks
- 3
- Avg merge
- 9h 12m
- Merged PRs (30d)
- 74
Description
Ex: shinyshadcn would vendor the JS that is currently available to the target app.
Then this opens shinyshadcn to freely update after the app has been initalized. shinychadcn should feel free to ruthlessly update to work as it wants... as any previous app has a local copy of js assets.
This gets the app author safety for working over time... even if shinychadcn does make breaking changes.
This gets the pkg author safety... as the current assets are only updated on command.
So, when making references packages (such as shinyshadcn), we should use this approach for pkg development for index.tsx apps
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
Start by tracing how reference packages such as shinyshadcn expose JavaScript to initialized index.tsx apps, and compare that with the current target-app asset flow. Done means secondary packages vendor a local copy of their JavaScript assets so initialized apps remain stable while package authors can update independently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- build-system, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100