webview_deno
node-v0.x-archive
webview_deno | node-v0.x-archive | |
---|---|---|
3 | 7 | |
1,372 | 34,925 | |
0.4% | - | |
5.0 | 0.0 | |
2 months ago | about 6 years ago | |
TypeScript | ||
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
webview_deno
-
Deno Webview DevTools?
I spun up the Deno Webview demo (https://github.com/webview/webview_deno) and compiled an EXE. When I run the EXE, I have two windows: the UI window and what I presume is the host process window. I only started learning Deno like yesterday but what's the state of DevTools for Deno Webview? Can I compile my Deno Webview executable with Chromium plugins like Chrome DevTools?
-
Use any web browser as GUI with Deno & WebUI Portable
By the way, I was using Deno + WebView 1.2k stars, and it's working fine, but my end-users need to install the WebView runtimes... so it wasn't portable. while WebUI is totally portable.
-
Deno 1.9 – native http2, performance boost, blob and import completion support
The most updated webview bindings I know of for deno: https://github.com/webview/webview_deno
It's likely you will find some hiccups in latest deno release because it uses rust plug-ins and they are getting overhauled at the moment. Maybe a few more months before getting stabilized.
node-v0.x-archive
-
Wizards of Opensource, Ep 1: Ryan Dahl
On 16 February 2009, a GitHub commit was made. By a person who would later turn out to be the creator of two of the most successful, impactful, and standard tech platforms the world has ever seen. Who is he? Let's explore.
- What is Buffer in Node?
-
Stop Wasting Connections, Use HTTP Keep-Alive
Based on several issues in the Node repository (nodejs/node-v0.x-archive#7729, nodejs/node-v0.x-archive#5488, nodejs/node#5436) this error can occur when a DNS server fail to respond, perhaps due to it rate-limiting requests. Reducing DNS lookups can reduce or eliminate these errors.
-
Why does RSS constantly grow when reading data from a child process and calling process.stdout.write()?
I don't know how node is processing the stream and buffering or not buffering. I just invested the past few hours into researching Node.js buffering and not buffering read(). There are more than one issue regarding the subject-matter, e.g., https://github.com/nodejs/node/issues/2972, https://github.com/nodejs/node-v0.x-archive/issues/4000, https://github.com/nodejs/node/issues/6379. From what I gather Node.js blames the process itself. However, I run the same algorithm using Python, C++, C, QuickJS JavaScript engine where the RSS does not exponentially increase during usage.
-
I am proud to announce, a new Sorting algorithm!
setTimeout implementation: https://github.com/nodejs/node-v0.x-archive/blob/master/lib/timers.js
-
Why console.log(this) prints an empty object when used in the global context? Shouldn't it point to the global object?
...or something similar to that. I mean, it's pretty close to that. You can see for yourself if you want. These lines there are exactly what they do: They set thisValueto point to module.exports and then they execute your file/module with that as the value of this. (Only they have some additional helper stuff like ReflectApply because there are some additional complexities now with modules. In the older versions of the code you could see the apply call directly there.
-
Deno 1.9 – native http2, performance boost, blob and import completion support
I was referring to node <0.1.30[1] which did have promises for a while. largely from jQuery deferred, which were ungood in a couple ways I don't remember. but also remarkably similar.
I still largely think kris kowal building the "Q" promise library is what made promises interesting, what surfaced the idea that we might want to first-class our completeablea/futures. I know kris had some specific inspirations but I forget what.
pains me somewhat to this day that promises ultimately became somewhat un-value like, that handlers don't get to see what it was resolving. all the chain/spawn discussion, the functional promise folk: they got rolled by those insisting we had to target only the lowest rings of the developership, and that allowing more potent systems was unacceptable. wish I could find those es-discusa threads, for the powerful sorrow of the afteath, what we are stuck with, in it's so lites form, haunts me. especially as we double back a decade latter & invent controllers & signals toanage our promises. which we would have had for free.
way off topic now. forgive me my late night ramblings.
[1] https://github.com/nodejs/node-v0.x-archive/blob/v0.1.30/Cha...
What are some alternatives?
deno_sdl2 - SDL2 module for Deno
samples - A collection of Flutter examples and demos
wpt - Test suites for Web platform specs — including WHATWG, W3C, and others
raptor - Asynchronous serverless engine powered by Deno
deno-udd - Update Deno Dependencies - update dependency urls to their latest published versions
deno_doc - Documentation generator for Deno
nodejs-advisory-board - Meeting Minutes and Working Group Discussions
tesla_auth - Securely generate API tokens for third-party access to your Tesla.
node - Node.js JavaScript runtime ✨🐢🚀✨
agentkeepalive - Support keepalive http agent.