I'm confused about whether onFocus/onBlur events should bubble in preact, like they do in React.

In this example using preact 10.0.0-beta.1 they don't bubble https://codesandbox.io/embed/5wxk9zk7lx

...whereas in the Preact repl they do bubble https://preactjs.com/repl

export default () =>(
  <div onFocus={() => console.log("FOCUS")}>
    <div>
      Focus this input
   

🐛 bug report

Description of the problem. How has this issue affected you? What are you trying to accomplish?

I tried to use react component like react-window in preact sandox which works perfectly fine locally but is not working in codesandbox.

Link to sandbox: preact-template-compat-issue

Root cause

Preact tr

I've been playing around with Razzle and how the Server HMR works.

I generated a Razzle Project and run it

• npx create-razzle-app my-app
• cd my-app && yarn start

If I now edit the src/Home.js I see hot reloading working in the browser and I see the server.js being re-required by the index.js. But if I open my dev tools "view page source" my changes are not actually in the HTML

    "nerv-create-class": "^1.3.3",
    "nerv-redux": "^1.3.3",
    "nervjs": "^1.3.3",
    "node-sass": "^4.9.2",
    "prop-types": "^15.5.8",
    "react": "^16.4.1",
    "react-dom": "^16.4.1",
    "react-loadable": "^5.5.0",
    "react-redux": "^5.0.7",
    "react-router-dom": "^4.2.2",
    "redux": "^4.0.0"

      'react': 'nervjs',
      'react-dom': 'nervjs',

I like your project a lot. I've been using it for a couple of months now. Just the demo folder never felt natural for me.
Simplify the project by integrating storybook instead of the demo folder.

then users can create documentation of their components.

I think it will benefit all library authors for React/Preact/ vue/ even javascript.

[Storybook](https://git

You might already know backpack or pocky which are kind of Poi for back-end (Node.js) apps.

So what about we making it possible as a poi preset 😄

But note that here we don't need the default poi command, since we don't need that dev server. Instead we use poi watch & nodemon to develop the app, each time webpac

JS 配置如下：

 var gitalk = new Gitalk({
            clientID: '3654916*****0c0038c28',
            clientSecret: 'd90d031a*****0e0fa4c7fe2fae747b96b',
            repo: 'Strange-AI.github.io',
            owner: 'Strange-AI',
            admin: ['jinfagang', 'Strange-AI'],
            id: vm.codeId,
            distractionFreeMode: false
        });
        gitalk.render('gitalk-conta

Do you want to request a feature or report a bug?
I guess is more feature request

What is the current behavior?
When the <> ... </> short form of fragments used with typescript, tsc gives the error:

`TS17016: JSX fragment is not s

I find it a bit awkward that for @babel/preset-env to use a .browserslistrc file (which is @babel/preset-env's default behavior when no targets is passed), I have to remember to pass targets: false: https://github.com/neutrinojs/neutrino/blob/master/packages/web/index.js#L116-L128

A the very least, I propose we look for a browserslist file, and if one is present, output a notice the con

First of all, congrats on the great project!
I've started using it a couple of days ago but I've now started to bump onto some very big hurdles due to the fact that the Readme and all of the currently available documentation is scattered across several docs, the micro bundle project and so on.
I'm afraid this issue will end up being kind of redundant but I was unable to find anywhere else where

Unistore will go very well with web components. It can have bindings for LitElement and others.

I am interested to work on this if it will accepted.

A minisite for jsxstyle would be a nice way to show off the things you can do with jsxstyle. As far as content goes, the README provides a decent starting point.

The idea of deferring state management to freactal is solid but as far as I can tell, users will still need to use class components if they want to trigger effects in lifecycle methods, and the README seems to imply that you can always use SFCs because freactal is orchestrating state, but that feels slightly misleading since React provides more than just state management APIs

Maybe add an e

Those who fail to find a document or an example refer here to resolve the issue first.
We are planned to build our official document site and before that is completed, please refer to the below link.

• Tutorial
  • ko: https://github.com/nhn/tui.grid/tree/master/packages/toast-ui.grid/docs/ko
  • en: https://github.com/nhn/tui.grid/tree/master/packages/toast-ui.grid/docs/en
• ex

npx create-react-app example --typescript
cd ./example

create jetpack.config.js from doc

jetpack --verbose
jetpack › Jetpack 0.12.1 �
jetpack › Webpack 4.28.3
jetpack › Dir G:\source\example
jetpack › Entry .
jetpack › Asset server http://localhost:3030
jetpack › Failed to compile! 

Please, could you provide detailed installation instructions and a complete list of all dependencies, including their versions?

Preferably in the form of a tutorial providing all steps, how to install starhackit on a particular vagrant box, e.g. on most recent Ubuntu.
I.e.:

• Install VirtualBox (version [VirtualBoxVersion] or higher) and [Vagrant](https://www.vagrantup.com/docs/getting-starte

Create a next.js template, to make it easier for people to adopt it.

Hey there! It seems with the current state of this boilerplate repo, when running "yarn dev" and updating any of the preact components, ReactDev tools loses it's node binding (see screenshot).

Steps to replicate:
1- checkout repo
2- $ yarn install
3

Brilliant package. I really like this.

Please consider renaming didSubscribe to didMount so that it is crystal clear what this is doing.

I'm not sure it is clear immediately to users how this aligns to React or Vue. The fact that didSubscribe isn't handled server side means that 'For handling side-effects upon first subscription.' isn't true in every circumstance.

The added advantage is t

Hello! Thanks again for making such an amazing little framework. preact-compat has been a dream to work with, and I'm excited to integrate. I've just run into one little issue, that I hope isn't a blocker, because the performance gains are tremendous! 🔥

I'll add as much code as possible, if it's relevant, note that our application runs fine in the browser, where this code isn't executed.

So

Right now the usage is just install instructions, should add a quick code snippet on loading a game 😄

activeClassName gets passed through to the a element as a regular attribute and is not used in the matching-style that is documented in the README.

It seems to be because the Link component defined in match.js is not actually exported. Instead the regular a passthrough component is exported.

https://github.com/preactjs/preact-router/blob/3eb5b31fe75c34672eeb13f2d310dee6d51b1f97/src