vanillaview
typescript-eslint
vanillaview | typescript-eslint | |
---|---|---|
6 | 123 | |
12 | 14,663 | |
- | 1.2% | |
0.0 | 9.9 | |
about 2 years ago | 3 days ago | |
JavaScript | TypeScript | |
MIT License | GNU General Public License v3.0 or later |
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.
vanillaview
-
Show HN: Bang
Hello Humans of HN,
This is BANG! a new UI framework for JavaScript on the web. It comes out of work I did in 2014 (on a web component framework with v0 Shadow DOM) and in 2018 (on a pure view-as-a-function of state framework with JavaScript template tag functions, variously known as brutal.js, dumbass and now vanillaview or just VV).
This work unifies those two works, and combines the JavaScript templating and minimal DOM updates (diffs without VDOM, by using granular updating functions down even to the level of splicing text nodes and text in attribute values and names) of VV with the scoped-styles, and component organization of the original unnamed web component framework.
It also adds a few new things, such as fixing some bugs in VV that I didn't even know existed before I tried merging it with another framework, making the list-diffing capability of VV truly minimal (previously it would reprint the whole list if any item order changed, not only items inserted or deleted actually are), and adding support for something I'm very proud of..."custom self-closing tags."
You can't get self-closing custom tags in HTML, because you can't define them. HTML has a limited set (, ,
and the like), but their syntax has always been neat. And React picked up on this as a way to include a component in another. I really liked that syntax. In VV I simply used template slots and function calls to the included view function to include components, it worked. But I always wanted a neater syntax. I experimented with a parser at the time, and that worked, too. But the performance was slow, and I thought it made the code clunky.One day I had the realization I could use HTML comment nodes. They look, "kinda" like elements, and you can write them by omitting everything but the leading ``. This was what I needed. Hence "bang" (at least I think that's where the name comes from, I'm not even sure). So these "bang tags" are self-closing tags, that are automatically converted to regular custom elements. Allowing you to type less.
I build things to improve my developer experience. That's all important. Then you're more efficient, and effective and you enjoy doing it more. So I'm sharing it here because I want to contribute to you, too. Maybe it's something valuable for you, or maybe it gives you ideas. Either way, this framework is yours. It's an open-source permissive license, and yours to contribute to, or fork or whatever.
It's got bugs right now and the syntax is more limited than VV, but I like it better. I wanted something new, and I got it. By making this. I can always add the VV syntax I removed for performance and simplicity during the merge, back later. But I'm not sure if I will, not yet. If you want something more battle-tested take a look at VV[0], but note that some of the fixes I made to the merged-VV have not been included back in main. I'm sure I'm going to do that eventually, but not for a while yet probably. I'm too busy basking in the bliss that is BANG!. Hopefully it's your bliss too :P ;) xx
[0]: https://github.com/i5ik/vanillaview
- Show HN: Vanillaview – Easy to Use Views in JavaScript
-
Show HN: Imba – I have spent 7 years creating a programming language for the web
Wow you are clearly a genius. The syntax looks beautiful! This is great. I don't want to use it (the best tool for the job for me is one that fits my own mental models, my own mind, and this is not it) but you are a genius.
Also -- wow those Nordics are super productive programmers/coders/developers/open-sorcerers (Sindre Aarsaether & Sindre Sorhus & Linus Torvalds & ......) -- could it maybe have something to do with: The low GNI, the high HDI and the great weather for coding? (cold, blistery, bleak, focused, electrons-and-light universe is only outlet in a desolate landscape)?
PS - I use my own memoized DOM with minimal/granular updates in my own quirky framework (https://github.com/i5ik/vanillaview)
CONGRATULATIONS, SIR!
- VanillaView is a JavaScript library for building user interfaces
- i5ik/vanillaview VanillaView is a JavaScript library for building user interfaces.
- Show HN: VanillaView – easy to use views with vanilla JavaScript semantics
typescript-eslint
-
Mastering Type-Safe JSON Serialization in TypeScript
Typescript-eslint can assist in this task. This tool helps identify all instances of unsafe any usage. Specifically, all usages of JSON.parse can be found and it can be ensured that the received data's format is checked. More about getting rid of the any type in a codebase can be read in the article Making TypeScript Truly "Strongly Typed".
-
Oxlint – written in Rust – 50-100 Times Faster than ESLint
> Only lint files that have changed? How hard that is?
Quite hard, especially since type-aware rules from e.g. https://typescript-eslint.io/ mean that changing the type of a variable in file A can break your code in file B, even if file B hasn't changed.
-
How to Do a TypeScript Conversion: an opinionated take on gradual conversions
The article only touches this: when converting to TypeScript, `any` is useful, but in the end you don't want this type in your codebase - so don't forget to use typescript-eslint [0] and turn on those no-unsafe-* rules which guard against `any` leaking into your code.
[0] https://github.com/typescript-eslint/typescript-eslint
- How do I add additional rules to my typescript-eslint settings?
- What's the best config for typescript-eslint?
- How do you add angular-eslint to your typescript-eslint config?
- What's the best typescript-eslint config?
-
The Best ESLint Rules for React Projects
By convention, React components should be named in PascalCase. @typescript-eslint has the config we need, and though we can't specifically target React components, we can target variables (and set some other conventions while we're at it):
- Open source public fund experiment - One and a half years update
- Never touch those //ts-ignores
What are some alternatives?
pFreak - pFreak is a unit-level 2-in-1 JavaScript benchmarking and testing framework.
eslint-config-google - ESLint shareable config for the Google JavaScript style guide
_____ - 💎 Das Bang-Architektur-Rahmenwerk! ist eine Ansichtsbibliothek, die benutzerdefinierte Elemente für das neue Zeitalter druckt. Es enthält asynchrone Vorlagenwerte, JS-Vorlagensyntax, <!void-elements /> und minimale DOM-Aktualisierungen ohne virtuelles DOM. [Moved to: https://github.com/i5ik/das.bang.froomwerk]
angular-eslint - :sparkles: Monorepo for all the tooling related to using ESLint with Angular
kotlinx.html - Kotlin DSL for HTML
ts-standard - Typescript style guide, linter, and formatter using StandardJS
coffeesense - IntelliSense for CoffeeScript. LSP implementation / VSCode extension
zod - TypeScript-first schema validation with static type inference
typescript-imba-plugin - Typescript Plugin for providing rich language functionality for Imba
node-clinic - Clinic.js diagnoses your Node.js performance issues
ts-node - TypeScript execution and REPL for node.js
WSL - Issues found on WSL