Skip to content

Conversation

@ianhi
Copy link
Collaborator

@ianhi ianhi commented Jan 14, 2026

adds a pixi setup to make it easier to get a working dev env.

I also find that pixi plays much more nicely with coding agents than conda/mamba

I didn't add the lock file as I think it's mostly bloat for the development pattern of this repo. I'd also like to look into removing yarn.lock as a bloat (hasn't been udpated in 2 years)

🤖 changes are by claude fully directed by me

@github-actions
Copy link
Contributor

Binder 👈 Launch a binder notebook on branch ianhi/ipympl/ian/pixi-setup

ianhi and others added 4 commits January 14, 2026 10:42
- Initialize pixi with pyproject format (integrated into pyproject.toml)
- Add jupyterlab, yarn, and nodejs dependencies
- Enables jlpm for building JavaScript/TypeScript code
- Lock file for reproducible builds
- Update .gitignore for pixi artifacts

Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
- Add pixi as recommended development environment setup
- Update all commands to use 'pixi run' prefix
- Fix watch command to use 'npm run watch' instead of 'jlpm watch'
- Keep conda/mamba instructions as alternative
- Clarify that pixi handles both Python and Node.js dependencies
- Add note about matplotlib requiring compiled dependencies

Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
- Assume JupyterLab by default (most common workflow)
- Include watch mode commands in initial setup
- Simplify "How to see your changes" section
- Move classic notebook setup to end as optional
- Group commands more logically
- Remove redundant explanations

Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
- Ignore .yarn/ directory (yarn cache and plugins)
- Ignore package-lock.json (npm lock file)
- These are build artifacts that shouldn't be committed

Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
Copy link
Member

@martinRenou martinRenou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! No strong opinion on this myself. As long as we don't force devs to use something I'm good 👍🏽

@ianhi
Copy link
Collaborator Author

ianhi commented Jan 14, 2026

will push a few changes I've found necesary now that im using this. then will merge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants