widgetti / widgetti/ipyreact

Have minimal fluff example and full production example

Open
#18 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
134
Forks
9
PR merge metrics
No merged PRs in 30d

Description

In another project, I am dealing with yet more build system churn. My project used to build, I turned on eslint, made suggested fixes, and it stopped running a full python build (yarn run build still works). I had a thought. This is a general point, not about anything specific we're doing with IPYReact yet.

For production you of course want all strictness and errors turned up. For dev, especially exploratory dev its useful to slowly turn these features on... to just get something working first.

It's helpful to have simpler examples that require less build carefullness so ideas can be tried out. If I'm developing, I just want to be able to import your code without having the exact same build config.

BTW the problem I just fixed was remedied by replacing

import * as data from '../package.json';

with

const data = require('../package.json');

the import syntax made eslint happy, but conflicted with something in the jupyter buildchain.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

No repository file or test is named. Start by reviewing the existing examples and build configuration around yarn run build, then compare the ESLint and Jupyter buildchain requirements; done means the issue's minimal-development and full-production examples are both defined and usable.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter, python, typescript
Domain
developer-experience, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.