A virtual DOM library with focus on simplicity, modularity, powerful features and performance.
@fuunnx @sebovzeoueb another solution besides using webpack@next is to use an alias in webpack.config
module.exports = {
...
resolve: {
alias: {
snabbdom: path.resolve(__dirname, 'node_modules', 'snabbdom', 'build', 'package')
}
}
}Then for TypeScript in the tsconfig
{
...
"paths": {
"snabbdom/*": ["node_modules/snabbdom/build/package/*"]
}
}
}
I'm making a simple test project to show off snabbdom and stuff that I used to do doesn't work anymore :D
h('div.button', {on: {click: e => send({type: 'increment'})}}, 'Increment'),
h('div.button', {on: {click: [send, {type: 'increment'}]}}, 'Increment'),
top one works as intended, bottom one the mouse event is being sent to the send function instead of that object
the documentation suggests that the bottom one should still work
is this a bug or has 2.0 changed the way this feature works?
would be nice to know if there's a good reason to upgrade
I'm currently on 1 with current projects
@patomation have you tried
browser-env ? it's a pretty reasonable shim for getting some window-like globals into node processes. I've used it for testing other dom related stuff: https://www.npmjs.com/package/browser-env
@mreinstein is my issue above what's referred to as loaded/carrying eventlisteners?
or did I find a bug?
a bit confusing to have it on the project's landing page if it's no longer supported
if it's on the landing page, my guess would be that it's gotten enough questions around it that someone thought it wise to put it directly on the readme in an effort to reduce the github issue noise. An exceptional situation. ;) I think probably it could be removed from the readme at some point, as 2.0 release date slides further into history
Had that section been deleted I would have noticed that it was no longer listed as a feature, which it currently is quite prominently
how the heck do I build this thing?
npm run compile results in javascript files that do not work in the browser as is
that the closetest I found!
Hello, I'm using a framework that uses snabbdom under the hood and I'm having a problem where HTML entities like
& and are being renderer as text (i.e. you literally see the characters on the screen, not the symbol) - anyone know what might be going on there? (There's a good chance this isn't snabbdom related, I'm out of practice... :-) )
nothing gets escaped there so it will literally display
a & b, or a & b
out of curiosity, has anybody managed to use
<template> properly ?
I am trying to figure out what exactly I need to repro this html:
<div>
<template>
<style>h1 { color: red; }</style>
</template>
</div>
I tried
h("div", {}, [
h("template", {}, [h("style", {}, "h1 { color: red; }")]),
])
and it's almost there but the style is not quite inside the template as a proper document fragment (I also tried to use the new
fragment function from snabbdom but I can't seem to get it to properly generate a fragment inside the template)
this is what I want to generate ^^
(notice how in the snabbdom output the
<style> is NOT inside the #document-fragment). This is driving me nuts :-)
Im trying to use styleModule props delayed and remove
although this works, typescript keeps erroring at compile
although this works, typescript keeps erroring at compile
Property 'delayed' is incompatible with index signature.
Type '{ opacity: string; }' is not assignable to type 'string' style: {
opacity: '0',
transition: 'opacity 1s',
delayed: { opacity: '1' }
}