IPYReact sample mono-repo starter project
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 134
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
I am looking at porting my package over to ipyreact to have a better supported buildchain.
Here is what I would like (and will stumble at points while building).
- a single repo with python and js code
- the JS inside that repo should be separate and look like a normal JS package to a js dev looking at it.
- The JS should build and push to an NPM module and function as a JS module wihtout needing any of ipyreact, esbuild, backbone, or ipywidgets js code
- The python code should use the ESM module pattern and build properly
nice to haves
local-dev mode where you can write JS features and have them avaiable to IPYReact without having to publish to npm, for local development
The stack that I have very close to working
I followed a vite demo and can build a package that works (minus css) with IPYReact.
Do you have a strong preference for another JS Build stack?
Is this project interesting to you? I think it will be useful for asking debugging questions even if you don't include it in official docs.
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 reviewing the Vite demo and the existing repository build setup described in the issue. Define the single-repository layout, independent JavaScript package build, Python ESM integration, and local-development workflow; done means the JavaScript package builds independently and the Python package builds and works with it without publishing for every local change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, typescript, vite
- Domain
- build-system, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100