alem.forge42.dev
A journey of a thousand miles begins with a single step
👨💻 Co-founder @forge42.dev
📚 Helping you learn remix.run
🤓 remix-development-tools, remix-hook-form, remix-toast, vite-plugin-icons-spritesheet, remix-client-cache creator
📹 YouTube AlemTuzlak
268 posts
1,187 followers
138 following
Regular Contributor
Active Commenter
comment in response to
post
Thank you for watching!
comment in response to
post
this is not directed at anyone in particular that's a part of this thread excluding me, and more than anything else it's not personal, but I hate your guts.
Thanks for coming to my ted talk.
Jokes aside, I hate it too, I'd rather get insulted than get insulted followed up by one of these
comment in response to
post
Awesome video, but obviously due to being a talk, Daniel had to skip across a lot of nuance so he can create an awesome framework in 40m, I feel like if he explained everything in detail it would be like a 10h talk.
I guess my example of a framework was more to say "touch all the points of vite"
comment in response to
post
True, although I feel like I'm a long way off from getting to a point where I would feel remotely confident in creating tutorials and resources for vite 🫣
comment in response to
post
comment in response to
post
I think what's important is that you understand what you're talking about, I just thought they would be the best candidates for the job, but people adjecent would also be cool, I've built 3 OSS plugins for Vite but still feel like I don't know anything about it 😅
comment in response to
post
I'll be back in 40m 😂
comment in response to
post
indeed it would!
comment in response to
post
And sometimes this is overwhelming because I don't know which of the 5 potential API's I should use to implement something as I don't understand the subtle differences between them, eg should I AST transform something, or use a virtual module then just call it.
comment in response to
post
Stuff like that, the link I haven't went through in details but the first two sections look like what I meant where they explain when to use certain things by using an example implementation, but as you already know, vite has a LOT to offer in terms on config options.
comment in response to
post
I think this is close to what I had in mind, something that explains stuff like:
- when do I use config vs configResolved
- how do I test the plugin and make sure it works as expected
- when do I use stuff like load, transform etc
- when to enforce something "pre", "post" etc.
comment in response to
post
Will it include testing the plugins as well 👀
comment in response to
post
This is a great starting point, I can't comment on the whole scope of it until I go through it!
comment in response to
post
I wish 😭
comment in response to
post
No worries, wishing you the best of luck in the job hunt 🙏
comment in response to
post
It's hidden in the name EU-rope 😂
comment in response to
post
Yes, I'm in Europe (not the cool part of EUrope) and found a job through them
comment in response to
post
That I believe you, have you tried g2i?
comment in response to
post
lol that will definitely do it! I was super confused as by default it doesn't get included unless you specifically set it to true
comment in response to
post
react-router-devtools.forge42.dev/docs/main/ge... this was just a boolean before IIRC
comment in response to
post
hmm you can just disable them completely with includeInProd: false
comment in response to
post
What are you bringing us? 🥰🫣
comment in response to
post
Ahh yes if you put it like that it makes total sense! 😂
comment in response to
post
So you're going with the net negative I see 😂
comment in response to
post
Thank you so much 🙏🙏
comment in response to
post
Balkan IT experience described in one post
comment in response to
post
Then you have pulled a miracle my friend!
comment in response to
post
Just don't tell them you support react-router and you're good
comment in response to
post
Yeah, I saw unfortunately, I was hoping it's not a big change to add, but seems as though it is. I'll do my best to figure out a different solution that doesn't make them have to rewrite typescript 😅
Any feedback is appreciated though!
comment in response to
post
why not --template=react-router-v7
comment in response to
post
It is possible, but I'm trying to get a nicer way to do it instead of having like 10~ tsconfig files, I've also added that as a comment here:
github.com/microsoft/Ty...