Tony Crowe
Tony Crowe
If you take this: https://github.com/marko-js/marko/blob/master/src/runtime/vdom/morphdom/index.js#L44 ...and patch it like so: ```js function compareNodeNames(fromEl, toEl) { return fromEl !== undefined && toEl !== undefined && fromEl.___nodeName === toEl.___nodeName; } ``` ...then...
Even with the workaround patch there are some inconsistencies which I cannot understand yet. I built this repo to test some ideas. https://github.com/tcrowe/isomorphic-marko-template @reytech-dev Maybe you can fork and reproduce...
Good question. I wont speculate either. (well only a little) One idea I can think of is that you can index all the assets and get access to it for...
I tried LokiJS, nedb, lowdb, and some others. Warehouse has a nicer API. We just need to document it better and support with examples.
Agreed. This documentation could be improved with examples and more help. Thank you, @zwazoe
Is this still a problem? We recently updated the module too.
I don't know if this is the same bug but I did get a very weird problem with a large post. As you can see in the image it had...
I tried it again with your theme (very nice!) but I did not reproduce the error. If you would please try a few things: Somewhere around here: https://github.com/hexojs/hexo-browsersync/blob/master/lib/browsersync.js#L31 Add: ```js...
Do you know how to get a failing test case for this, @Anapopo ? We could not reproduce the error.
@fatfatson 🤔 That's interesting you may have found a solution after all this time. We could not reproduce it. Were you able to? If so, how?