HTML Nestings such as a <p> inside a <p> is invalid and browser automatically fixes it by putting the <p> outside the parent <p> and so the DOM ends up rendering different structure than JSX. There are a lot of such invalid nestings. See [this](https://github.com/MananTank/validate-html-nesting/blob/main...) For Example.
This is problematic and creates all sorts of bugs in Frameworks. Most Frameworks that use JSX (such as React, SolidJS, Preact) checks for invalid HTML Nestings at runtime and logs an error. ( Though this runtime checks are not very comprehensive - React has decent list of checks but is still missing quite a few )
Until now there was no way to check for such invalid Nestings without running the code. So I've created this ESLint Plugin to do just that.
This does not mean that we get rid of runtime invalid nesting checking, because This ESLint plugin can not predict what your component's top level element will be - because that would require running the code. So consider this as a tool to catch 99% of the invalid nestings without running the code.
Yeah, the terminology is a bit loose here, A better name would be "carousel", but "slider" seems to be more popular term for "carousel" nowadays. See https://www.npmjs.com/search?q=slider
This is definitely annoying, This is happening because I've added a logic that does not let the user trigger another transition if the slider is in mid-transition state.
Though I think a better approach would be to allow the user to trigger another transition and handle it gracefully.
I've been pretty disappointed with existing slider libraries because of their horrendous impact on the browser's main thread, and they also cause layout shifts which is a total pain in the neck to get rid off - They do not provide any way to fix the layout shifts in a idiomatic way.
So, I decided to create a slider library that focuses purely on being as fast as possible but still pretty push fully featured and super customizable. The library I have created is 30x faster than slick, 15x faster than swiper - while still being 5x smaller than slick and 19x smaller than swiper in size.
Despite being so small and fast - it still has lots of features and customizability.
This is problematic and creates all sorts of bugs in Frameworks. Most Frameworks that use JSX (such as React, SolidJS, Preact) checks for invalid HTML Nestings at runtime and logs an error. ( Though this runtime checks are not very comprehensive - React has decent list of checks but is still missing quite a few )
Until now there was no way to check for such invalid Nestings without running the code. So I've created this ESLint Plugin to do just that.
This does not mean that we get rid of runtime invalid nesting checking, because This ESLint plugin can not predict what your component's top level element will be - because that would require running the code. So consider this as a tool to catch 99% of the invalid nestings without running the code.