negomi/react-burger-menu — a UI/UX project — sits at 5.1k GitHub stars in the UI / UX space. :hamburger: An off-canvas sidebar component with a collection of effects and styles using CSS transitions and SVG path animations
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
An off-canvas sidebar React component with a collection of effects and styles using CSS transitions and SVG path animations.
Using Redux? Check out redux-burger-menu for easy integration of react-burger-menu into your project.
Demo & examples
Live demo: negomi.github.io/react-burger-menu
To build the examples locally, first make sure you're using Node <11.0.0. Then run:
npm install
npm start
Then open localhost:8000 in a browser.
Tests
The test suite uses Mocha, Chai and Sinon, with jsdom.
To run the tests once, run:
npm test
To run them with a watcher, run:
npm run test:watch
Installation
The easiest way to use react-burger-menu is to install it from npm and include it in your own React build process (using Browserify, Webpack, etc).
You can also use the standalone build by including dist/react-burger-menu.js in your page. If you use this, make sure you have already included React, and it is available as a global variable.
Version 3.x uses Hooks, so if you're using React 16.8+:
npm install react-burger-menu --save
If you're using an earlier version of React:
npm install react-burger-menu@^2.9.2 --save
Usage
Items for the sidebar should be passed as child elements of the component using JSX.
import { slide as Menu } from 'react-burger-menu'
class Example extends React.Component {
showSettings (event) {
event.preventDefault();
.
.
.
}
render () {
// NOTE: You also need to provide styles, see https://github.com/negomi/react-burger-menu#styling
return (
<Menu>
<a id="home" className="menu-item" href="/">Home</a>
<a id="about" className="menu-item" href="/about">About</a>
<a id="contact" className="menu-item" href="/contact">Contact</a>
<a onClick={ this.showSettings } className="menu-item--small" href="">Settings</a>
</Menu>
);
}
}
Animations
The example above imported slide which renders a menu that slides in on the page when the burger icon is clicked. To use a different animation you can substitute slide with any of the following (check out the demo to see the animations in action):
slide
stack
elastic
bubble
push
pushRotate
scaleDown
scaleRotate
fallDown
reveal
Properties
Some animations require certain other elements to be on your page:
Page wrapper - an element wrapping the rest of the content on your page (except elements with fixed positioning - see the wiki for details), placed after the menu component
If you are using an animation that requires either/both of these elements, you need to give the element an ID, and pass that ID to the menu component as the pageWrapId and outerContainerId props respectively.
Check this table to see which animations require these elements:
Animation
pageWrapId
outerContainerId
slide
stack
elastic
✓
✓
bubble
push
✓
✓
pushRotate
✓
✓
scaleDown
✓
✓
scaleRotate
✓
✓
fallDown
✓
✓
reveal
✓
✓
Position
The menu opens from the left by default. To have it open from the right, use the right prop. It's just a boolean so you don't need to specify a value. Then set the position of the button using CSS.
<Menu right />
Width
You can specify the width of the menu with the width prop. The default is 300.
You can control whether the sidebar is open or closed with the isOpen prop. This is useful if you need to close the menu after a user clicks on an item in it, for example, or if you want to open the menu from some other button in addition to the standard burger icon. The default value is false.
// To render the menu open
<Menu isOpen />
<Menu isOpen={ true } />
// To render the menu closed
<Menu isOpen={ false } />
You can see a more detailed example of how to use isOpen here.
Note: If you want to render the menu open initially, you will need to set this property in your parent component's componentDidMount() function.
Open menu handler
If you keep the menu state yourself it might be convenient to pass a custom function to be used when the user triggers something that should open the menu.
Called when:
The user clicks on the burger icon
<Menu onOpen={ handleOnOpen } />
Note: The menu will NOT open automatically if you pass this prop, so you must handle it yourself.
Close menu handler
If you keep the menu state yourself it might be convenient to pass a custom function to be used when the user triggers something that should close the menu.
Called when:
The user clicks on the cross icon
The user clicks on the overlay
The user hits the escape key
<Menu onClose={ handleOnClose } />
Note: The menu will NOT close automatically if you pass this prop, so you must handle it yourself.
State change
You can detect whether the sidebar is open or closed by passing a callback function to onStateChange. The callback will receive an object containing the new state as its first argument.
By default, the menu will close when the Escape key is pressed. To disable this behavior, you can pass the disableCloseOnEsc prop. This is useful in cases where you want the menu to be open all the time, for example if you're implementing a responsive menu that behaves differently depending on the browser width.
<Menu disableCloseOnEsc />
Custom keydown handler
For more control over global keypress functionality, you can override the handler that this component sets for window.addEventListener('keydown', handler), and pass a custom function. This could be useful if you are using multiple instances of this component, for example, and want to implement functionality to ensure that a single press of the Escape key closes them all.
Note: Using this prop will disable all the default 'close on Escape' functionality, so you will need to handle this (including determining which key was pressed) yourself.
Overlay
You can turn off the default overlay with noOverlay.
<Menu noOverlay />
You can disable the overlay click event (i.e. prevent overlay clicks from closing the menu) with disableOverlayClick. This can either be a boolean, or a function that returns a boolean.
You can disable all transitions/animations by passing noTransition.
<Menu noTransition />
This is useful if you want the menu to remain open across re-mounts, for example during SPA route changes.
Custom icons
You can replace the default bars that make up the burger and cross icons with custom ReactElements. Pass them as the customBurgerIcon and customCrossIcon props respectively.
You should adjust their size using the .bm-burger-button and .bm-cross-button classes, but the element itself will have the class .bm-icon or .bm-cross if you need to access it directly.
You can also disable the icon elements so they won't be included at all, by passing false to these props.
This can be useful if you want exclusive external control of the menu, using the isOpen prop.
Custom ID and/or classNames
There are optional id and className props, which will simply add an ID or custom className to the rendered menu's outermost element. This is not required for any functionality, but could be useful for things like styling with CSS modules.
<Menu id={ "sidebar" } className={ "my-menu" } />
You can also pass custom classNames to the other elements:
Note: Passing these props will prevent the menu from applying styles to the html or body elements automatically. See here for more explanation.
Focusing the first menu item
By default, the menu will set focus on the first item when opened. This is to help with keyboard navigation. If you don't want this functionality, you can pass the disableAutoFocus prop.
<Menu disableAutoFocus />
Custom item list element
The menu's children are all wrapped in a nav element by default, as navigation is likely the most common use case for this component. However, it's a general purpose sidebar, so you can change this to a div if you're not using it for navigation:
<Menu itemListElement="div" />
Styling
All the animations are handled internally by the component. However, the visual styles (colors, fonts etc.) are not, and need to be supplied, either with CSS or with a JavaScript object passed as the styles prop.
CSS
The component has the following helper classes:
/* Position and sizing of burger button */
.bm-burger-button {
position: fixed;
width: 36px;
height: 30px;
left: 36px;
top: 36px;
}
/* Color/shape of burger icon bars */
.bm-burger-bars {
background: #373a47;
}
/* Color/shape of burger icon bars on hover*/
.bm-burger-bars-hover {
background: #a90000;
}
/* Position and sizing of clickable cross button */
.bm-cross-button {
height: 24px;
width: 24px;
}
/* Color/shape of close button cross */
.bm-cross {
background: #bdc3c7;
}
/*
Sidebar wrapper styles
Note: Beware of modifying this element as it can break the animations - you should not need to touch it in most cases
*/
.bm-menu-wrap {
position: fixed;
height: 100%;
}
/* General sidebar styles */
.bm-menu {
background: #373a47;
padding: 2.5em 1.5em 0;
font-size: 1.15em;
}
/* Morph shape necessary with bubble or elastic */
.bm-morph-shape {
fill: #373a47;
}
/* Wrapper for item list */
.bm-item-list {
color: #b8b7ad;
padding: 0.8em;
}
/* Individual item */
.bm-item {
display: inline-block;
}
/* Styling of overlay */
.bm-overlay {
background: rgba(0, 0, 0, 0.3);
}
JavaScript
The same styles can be written as a JavaScript object like this:
How active is development on negomi/react-burger-menu?
The most recent commit recorded on negomi/react-burger-menu was 1.0 years ago, based on the GitHub push timestamp. The repository has 568 forks — one of the better signals of community interest.
How many stars does negomi/react-burger-menu have?
negomi/react-burger-menu has 5.1k GitHub stars — refresh the page for the live number, or check github.com/negomi/react-burger-menu. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
What else is in the UI / UX space?
negomi/react-burger-menu is tracked by TopGit under the UI / UX category, alongside 6 GitHub-tagged topics. Trending and Topics pages list peer repositories of comparable stars and language.
What language is negomi/react-burger-menu written in?
negomi/react-burger-menu is written primarily in JavaScript. GitHub's language field is based on the largest share of bytes in the default branch.
What topics is negomi/react-burger-menu associated with?
GitHub's repository topics for negomi/react-burger-menu: "animations", "component", "hamburger-menu", "react", "sidebar", "transitions". TopGit's editorial category is UI / UX.
Where do I read more about negomi/react-burger-menu?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/negomi/react-burger-menu is the definitive source.
Why is negomi/react-burger-menu categorized under UI / UX?
TopGit places negomi/react-burger-menu in the UI / UX category based on its GitHub topics and description (tagged: "animations", "component", "hamburger-menu"). Categories are assigned from real repository metadata, not editorial guesswork.
Read full README in the tab above.
Is react-burger-menu worth your time?
ChatGPT, Claude and Perplexity can all read this page. Ask one of them what it makes of react-burger-menu.