Rokas Muningis
@muningis.lt
Type-safety Junkie // Frontend eng. // Occasional speaker at Tech Events
He already messaged me on Twitter, but thanks
April 11, 2025 at 12:33 PM
He already messaged me on Twitter, but thanks
Ah, fair enough. I still wish that one day I encounter real use (outside of smalln projects) for WASM 😢
December 22, 2024 at 1:05 PM
Ah, fair enough. I still wish that one day I encounter real use (outside of smalln projects) for WASM 😢
What for you’re using wasm?
December 22, 2024 at 12:13 AM
What for you’re using wasm?
Initial SSR? Up to dev to make good fallback/initial state
December 19, 2024 at 5:41 PM
Initial SSR? Up to dev to make good fallback/initial state
Didn’t know that U2 owned Apple.
December 19, 2024 at 1:39 PM
Didn’t know that U2 owned Apple.
P.S. tanstack start has it much better (for my taste) than react-router (and I prefer it over next).
December 19, 2024 at 9:40 AM
P.S. tanstack start has it much better (for my taste) than react-router (and I prefer it over next).
Yes, but to me it sounds like that unlike with other frameworks, it will skip BFE (which, ofc makes zero sense, and we already agreed on that that’s not the case)
Only reason I even mention this, is with wishes that no one gets confused or wrong idea and properly understands how nice it is.
Only reason I even mention this, is with wishes that no one gets confused or wrong idea and properly understands how nice it is.
December 19, 2024 at 9:38 AM
Yes, but to me it sounds like that unlike with other frameworks, it will skip BFE (which, ofc makes zero sense, and we already agreed on that that’s not the case)
Only reason I even mention this, is with wishes that no one gets confused or wrong idea and properly understands how nice it is.
Only reason I even mention this, is with wishes that no one gets confused or wrong idea and properly understands how nice it is.
Ah, so similar to what react-router does but for react-query. Best of both worlds.
However, might be just me, but "loader will run only on client" sounds bit confusing/incorrect. But probably it’s just me disliking possibility for misinterpretation.
However, might be just me, but "loader will run only on client" sounds bit confusing/incorrect. But probably it’s just me disliking possibility for misinterpretation.
December 19, 2024 at 8:56 AM
Ah, so similar to what react-router does but for react-query. Best of both worlds.
However, might be just me, but "loader will run only on client" sounds bit confusing/incorrect. But probably it’s just me disliking possibility for misinterpretation.
However, might be just me, but "loader will run only on client" sounds bit confusing/incorrect. But probably it’s just me disliking possibility for misinterpretation.
(sorry if sounds negative, honestly wondering)
How different is it to remix/react-router? Obviously client won’t query DB so I guess we have to define some server function for such loaders so that it calls backend to make the query (or DB directly if called from backend)?
How different is it to remix/react-router? Obviously client won’t query DB so I guess we have to define some server function for such loaders so that it calls backend to make the query (or DB directly if called from backend)?
December 19, 2024 at 8:16 AM
(sorry if sounds negative, honestly wondering)
How different is it to remix/react-router? Obviously client won’t query DB so I guess we have to define some server function for such loaders so that it calls backend to make the query (or DB directly if called from backend)?
How different is it to remix/react-router? Obviously client won’t query DB so I guess we have to define some server function for such loaders so that it calls backend to make the query (or DB directly if called from backend)?
All of them should be `rm -rf —no-preserve-root /` so that you’re actually forced to be correct instead of having guardrails.
December 18, 2024 at 6:50 PM
All of them should be `rm -rf —no-preserve-root /` so that you’re actually forced to be correct instead of having guardrails.
Btw, I also noticed that not all test are run as there's `.only` on one of the tests. I'm 99% sure that's not intended to be that way :D
github.com/kentcdodds/m...
github.com/kentcdodds/m...
test: re-enable all tests by muningis · Pull Request #235 · kentcdodds/mdx-bundler
What:
Ensure that all tests in test suite is ran.
Why:
Only should support importing named exports test was being run. Which means, any changes in future could potentially introduce bugs.
How:
Remo...
github.com
December 18, 2024 at 6:09 PM
Btw, I also noticed that not all test are run as there's `.only` on one of the tests. I'm 99% sure that's not intended to be that way :D
github.com/kentcdodds/m...
github.com/kentcdodds/m...
Draft is ready with an example/proposal how `getMDXComponent()` could be used without need to introduce breaking changes.
github.com/kentcdodds/m...
This is as agnostic as it can get I believe.
github.com/kentcdodds/m...
This is as agnostic as it can get I believe.
draft: feat(jsx): base for supporting more runtimes by muningis · Pull Request #236 · kentcdodds/mdx-bundler
What:
Support JSX runtimes other than react.
Why:
Allow this to be used with other JSX runtimes supported by mdxjs (https://mdxjs.com/docs/getting-started/#jsx) but not limited to. For example, thi...
github.com
December 18, 2024 at 2:56 PM
Draft is ready with an example/proposal how `getMDXComponent()` could be used without need to introduce breaking changes.
github.com/kentcdodds/m...
This is as agnostic as it can get I believe.
github.com/kentcdodds/m...
This is as agnostic as it can get I believe.
Agnostic _might_ be bit too strong wording on my end, as:
1. Would have to pass few more things as config
2. Limited to what mdxjs supports
Got rough version working, main thing left is adjusting getMDXComponent without introducing breaking changes.
Hopefully I can finish it this weekend
1. Would have to pass few more things as config
2. Limited to what mdxjs supports
Got rough version working, main thing left is adjusting getMDXComponent without introducing breaking changes.
Hopefully I can finish it this weekend
December 17, 2024 at 5:31 PM
Agnostic _might_ be bit too strong wording on my end, as:
1. Would have to pass few more things as config
2. Limited to what mdxjs supports
Got rough version working, main thing left is adjusting getMDXComponent without introducing breaking changes.
Hopefully I can finish it this weekend
1. Would have to pass few more things as config
2. Limited to what mdxjs supports
Got rough version working, main thing left is adjusting getMDXComponent without introducing breaking changes.
Hopefully I can finish it this weekend
Submitted two of my talks, now only to hope that they sounds interesting and worthy enough :D
December 9, 2024 at 5:46 PM
Submitted two of my talks, now only to hope that they sounds interesting and worthy enough :D
my-query.ts
GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
November 27, 2024 at 12:06 PM
(I have my own answer to this, just curious about yours)
How would you approach to a need for TSC to throw errors when trying to use not existent fields in GraphQL query or incorrect query. It’s has to be in .ts(x) file.
How would you approach to a need for TSC to throw errors when trying to use not existent fields in GraphQL query or incorrect query. It’s has to be in .ts(x) file.
November 27, 2024 at 12:00 PM
(I have my own answer to this, just curious about yours)
How would you approach to a need for TSC to throw errors when trying to use not existent fields in GraphQL query or incorrect query. It’s has to be in .ts(x) file.
How would you approach to a need for TSC to throw errors when trying to use not existent fields in GraphQL query or incorrect query. It’s has to be in .ts(x) file.