Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

HTTP2 in DoneJS

Open
#58 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
documentation

Research direction

Review the listed done-serve, done-ssr, incremental-renderer, and steal-push features and gather the existing DoneJS documentation about them. Define the release post's feature-focused scope, including whether incremental rendering belongs in this post, and confirm that each described HTTP2 feature is implemented before considering the post done.

Written by the indexing model from the issue text.

Description

A blog post announcing the release of HTTP2 support in DoneJS. This will include:

  • done-serve sets up an HTTP2 server if --key and --cert are provided (HTTP2 requires SSL).
  • done-ssr using PUSH on assets when in an HTTP2 server (note, this is currently only turned on for the incremental renderer, we can make it optional for the traditional renderer).
  • Integration with steal-push maybe? (not implemented yet).
    • Note that this can benefit HTTP1 as well by adding Preload headers (supported in Chrome and Safari (issue))
  • A little about incremental rendering and what it is (or should this be a separate post by itself?)

Note that I would like this to be a post about the features, not a guide. Perhaps there should be mini-guides about each feature and link to them from the blog post.

Dominant language
JavaScript
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from donejs/developer-relations

All issues in donejs/developer-relations

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.