0.0.3 • Public • Published


NPM version

Gitment is a comment system based on GitHub Issues, which can be used in the frontend without any server-side implementation.

Demo Page



  • GitHub Login
  • Markdown / GFM support
  • Syntax highlighting
  • Notifications from GitHub
  • Easy to customize
  • No server-side implementation

Get Started

1. Install

<link rel="stylesheet" href="">
<script src=""></script>

or via npm:

$ npm i --save gitment
import 'gitment/style/default.css'
import Gitment from 'gitment'

2. Register An OAuth Application

Click here to register an OAuth application, and you will get a client ID and a client secret.

Make sure the callback URL is right. Generally it's the origin of your site, like

3. Render Gitment

const gitment = new Gitment({
  id: 'Your page ID', // optional
  owner: 'Your GitHub ID',
  repo: 'The repo to store comments',
  oauth: {
    client_id: 'Your client ID',
    client_secret: 'Your client secret',
  // ...
  // For more available options, check out the documentation below
// or
// gitment.render(document.getElementById('comments'))
// or
// document.body.appendChild(gitment.render())

4. Initialize Your Comments

After the page published, you should visit your page, login with your GitHub account(make sure you're repo's owner), and click the initialize button, to create a related issue in your repo. After that, others can leave their comments.




Type: object

  • owner: Your GitHub ID. Required.
  • repo: The repository to store your comments. Make sure you're repo's owner. Required.
  • oauth: An object contains your client ID and client secret. Required.
    • client_id: GitHub client ID. Required.
    • client_secret: GitHub client secret. Required.
  • id: An optional string to identify your page. Default location.href.
  • title: An optional title for your page, used as issue's title. Default document.title.
  • link: An optional link for your page, used in issue's body. Default location.href.
  • desc: An optional description for your page, used in issue's body. Default ''.
  • labels: An optional array of labels your want to add when creating the issue. Default [].
  • theme: An optional Gitment theme object. Default gitment.defaultTheme.
  • perPage: An optional number to which comments will be paginated. Default 20.
  • maxCommentHeight: An optional number to limit comments' max height, over which comments will be folded. Default 250.



Type: HTMLElement or string

The DOM element to which comments will be rendered. Can be an HTML element or element's id. When omitted, this function will create a new div element.

This function returns the element to which comments be rendered.


Same like gitment.render([element]). But only renders the header.


Same like gitment.render([element]). But only renders comments list.


Same like gitment.render([element]). But only renders the editor.


Same like gitment.render([element]). But only renders the footer.


Initialize a new page. Returns a Promise and resolves when initialized.


Update data and views. Returns a Promise and resolves when data updated.

Post comment in the editor. Returns a Promise and resolves when posted.



Type: string

Returns a Promise and resolves rendered text.


Jump to GitHub OAuth page to login.


Log out current user.



Type: number

Jump to the target page of comments. Notice that page starts from 1. Returns a Promise and resolves when comments loaded.

Like current page. Returns a Promise and resolves when liked.


Unlike current page. Returns a Promise and resolves when unliked.



Type: string

Like a comment. Returns a Promise and resolves when liked.



Type: string

Unlike a comment. Returns a Promise and resolves when unliked.


Gitment is easy to customize. You can use your own CSS or write a theme. (The difference is that customized CSS can't modify DOM structure)

Use Customized CSS

Gitment does't use any atomic CSS, making it easier and more flexible to customize. You can inspect the DOM structure in the browser and write your own styles.

Write A Theme

A Gitment theme is an object contains several render functions.

By default Gitment has five render functions: render, renderHeader, renderComments, renderEditor, renderFooter. The last four render independent components and render function renders them together. All of them can be used independently.

You can override any render function above or write your own render function.

For example, you can override the render function to put editor before comments list, and render a new component.

const myTheme = {
  render(state, instance) {
    const container = document.createElement('div')
    container.lang = "en-US"
    container.className = 'gitment-container gitment-root-container'
     // your custom component
    container.appendChild(instance.renderSomething(state, instance))
    container.appendChild(instance.renderHeader(state, instance))
    container.appendChild(instance.renderEditor(state, instance))
    container.appendChild(instance.renderComments(state, instance))
    container.appendChild(instance.renderFooter(state, instance))
    return container
  renderSomething(state, instance) {
    const container = document.createElement('div')
    container.lang = "en-US"
    if (state.user.login) {
      container.innerText = `Hello, ${state.user.login}`
    return container
const gitment = new Gitment({
  // ...
  theme: myTheme,
// or
// gitment.renderSomthing(document.body)

Each render function should receive a state object and a gitment instance, and return an HTML element. It will be wrapped attached to the Gitment instance with the same name.

Gitment uses MobX to detect states used in render functions. Once used states change, Gitment will call the render function to get a new element and render it. Unused states' changing won't affect rendered elements.

Available states:

  • user: object. User info returned from GitHub Users API with two more keys.
    • isLoggingIn: bool. Indicates if user is logging in.
    • fromCache: bool. Gitment will cache user's information. Its value indicates if current user info is from cache.
  • error: Error Object. Will be null if no error occurs.
  • meta: object. Issue's info returned from GitHub Issues API.
  • comments: array. Array of comment returned from GitHub Issue Comments API. Will be undefined when comments not loaded.
  • reactions: array. Array of reactions added to current page, returned from GitHub Issues' Reactions API.
  • commentReactions: object. Object of reactions added to comments, with comment ID as key, returned from GitHub Issue Comments' Reactions API.
  • currentPage: number. Which page of comments is user on. Starts from 1.

About Security

Is it safe to make my client secret public?

Client secret is necessary for OAuth, without which users can't login or comment with their GitHub accounts. Although GitHub does't recommend to hard code client secret in the frontend, you can still do that because GitHub will verify your callback URL. In theory, no one else can use your secret except your site.

If you find a way to hack it, please open an issue.

Why does Gitment send a request to is an simple open-source service to proxy one request during users logging in. Because GitHub does't attach a CORS header to it.

This service won't record or store anything, only proxy and attach a CORS header to that request. So that users can login in the frontend without any server-side implementation.

For more details, checkout this project.

Package Sidebar


npm i gitment

Weekly Downloads






Last publish


  • imsun