Rename exported global from `hyperapp` to `Hyperapp`.
See original GitHub issueThis is a proposal only relevant to CDN users. If you are using ES5 or ES6 via a module bundler, etc., you have nothing to worry about.
Before
🚫 const { h, app } = hyperapp
After
✅ const { h, app } = Hyperapp
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Modules in V2 · Discussion #1020 · jorgebucaran/hyperapp
A) Increment and Decrement are completely unaware of the shape of the global app state. Their definitions are completely self contained. B) Main ......
Read more >hyperapp-render | Yarn - Package Manager
[BREAKING] Rename global exports from window.* to window.hyperappRender.* . [BREAKING] Rename server package from hyperapp-render/server to hyperapp-render .
Read more >https://raw.githubusercontent.com/frenzzy/hyperapp...
[BREAKING] Rename global exports from `window.*` to `window.hyperappRender.*`. - [BREAKING] Rename server package from `hyperapp-render/server` to ...
Read more >Hyperapp state machine web app - Gleb Bahmutov
How to write a web application using a state machine and Hyperapp framework. ... export default Machine({ ... import { app } from...
Read more >hyperapp - npm
The tiny framework for building hypertext applications.. Latest version: 2.0.22, last published: 9 months ago. Start using hyperapp in your ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
In a unexpected turn of events, I’m closing here and https://github.com/hyperapp/hyperapp/issues/352 and leaving things the way they are!
It is probably worth making clear that, for any apps/demos that rely on the
window.hyperapp
namespace already (codepens especially officials and forks), this is a breaking change.I prefer
hyperapp
and therefore would supporthyperappRouter
(camelCase module convention) on the grounds of, same advantages less disruption.Either way I will be happy if there is consistency 😃