#Remix Development Tools

1 messages · Page 3 of 1

lucid mesa
#

Thank you so much, will fix it asap!

#

So this part you could just add the embedded tools into there

#

Hmm but then again you still would bundle it in due to the plugin

#

I could add a flag

stiff remnant
#

🤔 yeah

lucid mesa
#

To ignore the panel

#

Bevause what the plugin does

#

It goes to your root imports the remix dev tools and wraps your default export

#

Due to the fact that it's an array of plugins I think it would be easy to ignore it with a flag

stiff remnant
#

I just had a thought

lucid mesa
#

You could technically just filter it out yourself

stiff remnant
#

what if you exported a context that could selectively disable the wrapper behavior? The default context value would be true or enabled or whatever to avoid breaking existing behavior

#

but then you could put the context value in your entry.client.tsx and then turn the plugin's runtime behavior on/off however you needed to

#

(just spitballing here)

#

that way you could always build with the Vite plugin in place, but then you'd get some runtime levers to pull

#

more than happy to submit a PR too with what I'm thinking, if that's more to your liking

lucid mesa
#

Tbh I'm very sick atm so my brain is only half working

#

So basically like <context><remixbrowser /></context>

stiff remnant
#

yeah basically

#

get some rest, I'll put a PR together and we can revisit it when you're feeling better 👍

lucid mesa
#

Sounds good, got a bit sick so yeah, but tbh I don't think that would be that hard

#

My birdies passing hit me a bit harder than I thought 😅

stiff remnant
#

😭 that sucks man, losing pets is hard

lucid mesa
#

Indeed it is coolpanic

lucid mesa
#

I've figured out why I couldn't reproduce it all this time, it's OSS specific I believe

#

ah yes, in stackblitz it doesn't work but it does on windows, freaking windows

full prism
lucid mesa
#

Not really, havent even heard of it

full prism
# lucid mesa Not really, havent even heard of it

Oh. It was written about heavily. They tried to put a version out months ago for some new variation of windows. People went nuts. The press picked it up.

It takes screenshot after screenshot of what you're doing on your machine like an employee spy. Then Copilot can tap into that for your own search, etc. But who knows who or what else.

Then, the broader universe discovered Msft, in a zeal to ship, I suppose, was storing all those pictures and information in a plain text file.

People went more nuts.

Microsoft ditched it. People breathed again. Then Microsoft, not to be deterred, announced it's coming back. This is the gist of how I remember it all. Many, many articles.

Ars has more. It was all very exciting:

https://arstechnica.com/gadgets/2024/09/microsoft-details-security-privacy-overhaul-for-windows-recall-ahead-of-relaunch/

lucid mesa
#

Oh my God that thing, so its called recall?

full prism
#

Yeah. Yours or Microsoft's, I don't know. Lol.

lucid mesa
#

I forgot about their announcement completely, hopefully that never gets added

full prism
#

Maybe it'll turn out to be OK, I don't know. We'll see.

lucid mesa
#

It can't turn out to be okay if they plan to SS my screen without consent lol

full prism
lucid mesa
#

Thanks to @stiff remnant I have finally fixed the issue of components/routes not opening up properly in vs code

#

on macOS systems

tawdry ice
#

Wildcard routes from remix would act as ENV vars
what

lucid mesa
#

yep 😄

#

on macOS when you do code ".path/to/$file"

tawdry ice
#

WINdows dev supremacy.

lucid mesa
#

it thinks ohhh okay $file is an env var

#

let me swap that

#

oh it doens't exist

#

empty string it is

#

#yolo

stiff remnant
lucid mesa
#

something's cooking

stiff remnant
#

I had to bypass the pre-commit hook because knip was complaining about pkg-pr-new being an unlisted binary

lucid mesa
#

You can add it to ignoredybinaries, will leave feedback today

#

Although at first glance I can tell you you broke rr7 support already😂

stiff remnant
#

orly... how so? (genuinely curious)

lucid mesa
#

left the comment on the PR

stiff remnant
full prism
stiff remnant
#

I want to be in control of how the dev tools are rendered, and where/when/how they're inserted into the DOM.

#

I already have a general "dev tools" floating button, don't want another one

full prism
#

Oh, that's right — you've got a tray of tools. I understand. It's a good idea.

#

Now, what would be really exciting, maybe, is if you hooked up the output of all those tools to a LLM, maybe even one you train, and maybe you could do something that looks more like magic than you've seen in a long time.

serene stratus
#

I'm currently experimenting with remix-devtools as I've just discovered it and after following the guide in the docs, the devtool component isn't rendered on the page

lucid mesa
#

with the vanilla setup?

lucid mesa
fickle shard
lucid mesa
fickle shard
#

view loader data, route maps, etc

#

By two parts I mean a hyphen

lucid mesa
#

aren't keywords for that?

fickle shard
#

Yeah but the description comes up in search too

#

I don’t know much about GitHub seo but this tactic feels portable to me

#

Increase the surface area with which your repo can touch search queries

lucid mesa
#

package name: "react-router-devtools-loaderdata-hydration-mismatch-other-debugging-stuff" 😂

#

I will add in a better description thanks for the tip

lucid mesa
#

exciting news for the next major!

late quartz
#

nice!!

lucid mesa
#

Won't work with CJS though, cough cough @stiff remnant

tawdry ice
#

coolpanic might as well be called :rossi:

stiff remnant
#

🤞 I have a PR in flight to ESM all the things

stiff remnant
#

The most painful bit by far was moving to moduleResolution: "NodeNext" oof for our shared packages

lucid mesa
stiff remnant
#

yeah it's weird for sure

#

apparently in TS 5.7 they're support rewriting *.ts -> *.js

lucid mesa
#

yeah I saw that, I dunno, adding extensions just feels wrong

#

no matter how good/bad it is for the compiler and everything else

stiff remnant
#

Honestly I think it's just more about the ESM requirement that module specifiers need to be valid URLs

#

but definitely awkward

lucid mesa
#

yeah, it's one of those things "hey i've gone 10-20 years not using extensions, why do I suddenly need to care now" 😅

lucid mesa
frosty raven
lucid mesa
lucid mesa
#

If you want to try this in a rr7 pre-release:

npm install https://pkg.pr.new/forge42dev/Remix-Dev-Tools/[email protected]
full prism
lucid mesa
full prism
frosty raven
lucid mesa
#

Did you configure it in any sense?

#

Did you add it before remix plugin?

frosty raven
#

Yes

lucid mesa
#

You have to add ?customFlag=true to the url

frosty raven
#

wait, where is that document? 😄

lucid mesa
#

Even comes with a warning 😂

frosty raven
#

Sorry mate, thanks for the help. I humbly apologise coolpanic

lucid mesa
#

No worries! Happy to help, hope you enjoy them!

lucid mesa
fickle shard
#

here's a copy button if anyone needs it

image.png
lucid mesa
#

Thanks chatGPT!

lucid mesa
#

support for deferred promises is now infinitely deep!

image.png
#

although please don't nest em @fickle shard

lucid mesa
crisp sun
# 
⚠️  remix-development-tools are going to be deprecated and will be renamed to react-router-devtools  when React Router v7 is released ⚠️ 
⚠️  Set suppressDeprecationWarning to true in your vite.config.ts file to silence this warning ⚠️
Re-optimizing dependencies because vite config has changed
12:38:25 PM [vite] server restarted.```
#

@lucid mesa is it going to be unmaintained?

lucid mesa
# crisp sun <@230092827684634625> is it going to be unmaintained?

Well, like the message says, it's going to be renamed to react-router-devtools which means moving forward you'll have to migrate to react-router v7 in order to get the latest and greatest out of the devtools, stuff like network tracing and single fetch full support

crisp sun
fickle shard
#

remix-development-tools has been renamed to react-router-devtools for support with React Router 7

#

Remix isn't deprecated, it just has a new name in the new version

lucid mesa
lucid mesa
fickle shard
#

that's all speculative

#

what's true right now is that Remix v2 exists and the next version of it is React Router 7

lucid mesa
fickle shard
#

yeah but that's bad messaging

#

it makes people not want to use them

#

if someone is planning on releasing a greenfield React Router 7 app one year from now, their best bet is to start with latest remix right now

#

if it's a good idea for them to start with remix devtools right now, then don't call them deprecated

#

deprecated and "there's a new version" are two different things

lucid mesa
#

i guess that's true

full prism
#

I see Jacob's point. I think you're damned if you do and damned if you don't.

I'm not a library author, but it does seem like Remix and React-Router will co-exist for awhile, which leaves you in an unenviable position. Maybe you could come up with a way to name it neutrally or dedicate the top of your ReadMe / docs to the two versions of your tool.

It's a pernicious problem, no doubt.

fickle shard
full prism
# fickle shard they co-exist in the same way that Remix v1 and Remix v2 co-existed

I'm still using a v1. I don't know. Sergio said the other day, it may be alive forever.

There's a lot of branches in the world of Remix. Versions, ESM compatibility or lack thereof. Now a new stack, maybe another later.

I like that Remix figures things out as it goes, but you can't really count anything out that way.

Anyway, as they say, what's in a name?

fickle shard
#

arrows by any other name would smell as wheat

#

or something like that

full prism
#

Yah. Roses and sweet.

lucid mesa
lucid mesa
#

I'm playing around with allowing you to register your custom events in the network tab

lucid mesa
ornate hull
#

I wonder if it's finally time for rdt and epic stack pr, curious Kent's thoughts on this

lucid mesa
#

Yeah I have no idea, you'd have to ask Kent, and I'm not really sure if he pays attention to this channel

#

Fun fact: I've written over 200+ tests for react-router-devtools and plan to add at least a hundred more before the official release to assure stability in the future!

fickle shard
#

Serves as a good example integration for anyone else too

green stream
#

Whats going on?

lucid mesa
green stream
#

Sheeesh it would take a lot of time cause of this project is kinda big

lucid mesa
#

also, just released 4.7.7 which completely removes remix-forge integration in rdt!

#

sorry to maybe 1 person who used it

green stream
#

Now it works! Ty ❤️

lucid mesa
#

Awesome 👌

full prism
#

Do you collect analytics about RDT usage? I thought Forge was clever, but only used it once or twice. It's a fiddly world inside code editors.

lucid mesa
#

Especially with single fetch now challenge

#

I wonder if there are any oss packages that do these kind of things, collect usage info etc 🤔 tbh not sure if that's even something i can legally do

full prism
lucid mesa
torpid jolt
#

Like the huge, red disclaimer kind.

lucid mesa
#

yeah I don't think people would like me doing so, even if it's just for my curiosity

fickle shard
#

you can do it, Next.js does

#

they use the NEXT_TELEMETRY_DISABLED=1 environment variable to opt out

lucid mesa
#

I guess if it's telemetry maybe it would work

#

any idea on how they do it Jacob?

full prism
#

Just to be fair, I didn't ask about data collection to encourage you to do it.
You just sounded like you knew about usage, so I was curious.

It's a futile point, but people despise tracking.

lucid mesa
#

I'm more thinking about the idea of how to pull that off in a sane manner and if it would be possible, I'll probably never add it, but as Justin Bieber once said: "Never say never"

fickle shard
median thistle
#

Way back in the dark ages, around 1990-ish, my office mate at grad school was big into the rewrite of gnuplot. He added the most basic telemetry to measure the number of installs: the install target on the makefile sent one single UDP packet to a server running on his workstation. Granted, these were the days when the entire NSFNet backbone ran at 256kbps, so minimizing traffic was important. 🙂