duojs and the frontend ecosystem
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 14
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Hey @maxogden,
When duojs add support to bower registry, it will be way much simpler to include frontend tools, like you've done here in this particular case.
I've had to include CodeMirror into a simple demo, and it's pretty straightforward to do it with Duo:
When they add support to read bower.json registry, it will be as simple as requiring codemirror/CodeMirror, instead of the full path as I've done.
Browserify is good for the frontend ecosystem but we need something smarter than that.
BTW this is not an issue, just a discussion. Nice job you've done here. :)
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
This is explicitly a discussion rather than an actionable issue, and it does not define a concrete change or completion criteria. Review the linked app.js, css.js, Makefile, and index.html examples, then investigate the referenced duojs issue about Bower registry support. A specific implementation scope and acceptance criteria would be needed before work can begin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100