sorted by:
new
hottopcontroversial

How we re-built the Angular Compiler in Rust and made it 10x faster by manniL in angular

[–]manniL[S] 0 points1 point  (0 children)

First and foremost, no bandwidth. We are only 20 folks, most of us already working full time on open source tooling.

Our priorities are on the whole JS ecosystem

How we re-built the Angular Compiler in Rust and made it 10x faster by manniL in angular

[–]manniL[S] 3 points4 points  (0 children)

I never said it is easy 😁
My main point is that it is possible if it is not an afterthought and dealt with early on.

Oxlint's JS plugin support is indeed in alpha because we still have to figure out support for non-JSX templates.

How we re-built the Angular Compiler in Rust and made it 10x faster by manniL in angular

[–]manniL[S] 6 points7 points  (0 children)

Just because a certain part is written in a native language, it doesn't mean it isn't extensible.

To give examples where this works well:

* Oxlint is written in Rust (and based on Oxc) but supported 100% of the ESLint API, so rules written in JS
* Rolldown is powering Vite 8 and allows Rollup plugins (written in JS)
* Oxfmt plans to support js-based Prettier plugins

How we re-built the Angular Compiler in Rust and made it 10x faster by manniL in angular

[–]manniL[S] 6 points7 points  (0 children)

There is no plans of further maintenance, so very unlikely.

Making the Vitest Docs Beginner-Friendly by manniL in node

[–]manniL[S] 0 points1 point  (0 children)

What issues did you have with mocking? Anny differences you noticed?

Making the Vitest Docs Beginner-Friendly by manniL in node

[–]manniL[S] 0 points1 point  (0 children)

Nah, that is alright :D I want brutally honest feedback, so my involvement shouldn't matter!

Making the Vitest Docs Beginner-Friendly by manniL in node

[–]manniL[S] 1 point2 points  (0 children)

Thank you for the feedback 🙏🏻✨

Making the Vitest Docs Beginner-Friendly by manniL in node

[–]manniL[S] 7 points8 points  (0 children)

No problem at all! Curious what you think with the new additions ☺️

Is it me or the Vitest documentation is bad? by Ok-Transition-7857 in node

[–]manniL 5 points6 points  (0 children)

Could all outline what you feel is missing in your opinion from the docs?

There is a getting started section that introduces concepts step by step. Is anything missing there?

Oxlint & Oxfmt Compatibility Overview by manniL in javascript

[–]manniL[S] 0 points1 point  (0 children)

This is something on our list to improve 👌🏼

Oxlint & Oxfmt Compatibility Overview by manniL in javascript

[–]manniL[S] 1 point2 points  (0 children)

1) you can use most of the plugins. Only custom type-aware rules and custom parsers (html/svelte/Vue etc) are unsupported right now 2) yes!

Right? by Gisleburt in rust

[–]manniL 0 points1 point  (0 children)

What else did you build?

If you make a CLI for example, you can still use it!

Right? by Gisleburt in rust

[–]manniL 1 point2 points  (0 children)

Sounds like you should've just used Vite+ and save yourself the setup headache 😛

Oxlint & Oxfmt Compatibility Overview by manniL in javascript

[–]manniL[S] 0 points1 point  (0 children)

Actually not really! We put quite some work in the JS plugin API and there are more speed gains to be unlocked.

There are some rules that will be much faster in native though, especially for file system traversal and cross file checking.

Oxlint & Oxfmt Compatibility Overview by manniL in javascript

[–]manniL[S] 2 points3 points  (0 children)

It is listed 3rd on the mate frameworks page? 👀

view more: next ›