**Nightscout Habanero is here!**
After long 9 months, Habanero brings you better compatibility with the latest browser versions and significantly faster loading speeds. There are no huge changes in the features so there’s no pressure to immediately update if Nightscout works for you, but we hope you’ll love you’ll love the speed improvements if you do.
**IMPORTANT!** if deploying the site to Azure, due to limitations in how Azure works, you have to ensure *WEBSITE_NODE_DEFAULT_VERSION* app setting is set to *8.5.0* for Nightscout to work
**Changes in Nightscout Habanero**
* Substantial improvements to the page loading speed
* New startup screen on app start, before we can render the graph
* Nightscout should consume significantly less data to load, helping those with low data caps
* Distribution reporting now filters CGM data for noise and shows additional glucose variability analysis
* Amazon Alexa support now supports localization
* Daily reports visualise total COB and IOB
* Localization support for Simplified and Traditional Chinese
* Many, many small bugs have been squished
* Several improvements to OpenAPS, Loop and AndroidAPS data visualisation & compatibility
* URL to access reporting, food editing, admin has changed, so update bookmarks if needed
* If-modified-since HTTP header support for CGM entry and treatments API to reduce data consumption* Compare reporting and chirp generation is no longer supported
**Known issues**
* Mouseover tips on menu buttons don’t work on all browsers
**Technical changes**
* The backend uses the latest Node 8.5.0 for hosting
* Almost all npm dependencies were updated to newer versions for 8.5.0 compatibility, compatibility with modern browsers and optimisation
* The dependency management has seen extensive changes
* We now use WebPack for the client dependency bundle generation
* Bower has been removed from dependency management chain altogether
* Bundle is created on npm dependency installation before app startup to speed up application start and reduce the memory footprint of the application
* Client assets are minified and compressed when in production hosting
* The app uses cache manifest for speeding typical loads
* Developers: use NODE_ENV = development to change caching behavior to be more development friendly
* HTML for views has been moved to the views folder and the app uses the ejs templating engine to render cache punch through tokens