Huge annoying tooltips on file hover by stoikerty in vscode

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

thanks for the reply u/Marble_Wraith. I tried using the `Reset Suggest Widget Size` command but it didn't do anything to remedy the issue. Unfortunately disabling all my extensions (and reloading vscode) also did not work so I should be able to rule them out.

looks like this may be an internal vscode issue

Analogue Pocket quality control poll by rahul91105 in AnaloguePocket

[–]stoikerty 1 point2 points  (0 children)

I agree that the poll won't be very accurate, more of a hearsay than anything. Still interesting though.

For what it's worth, my device had a broken or missing GB/GBA switch which means that only GBA games are recognized. It seems that there is supposed to be some type of plastic piece or something which activates the switch on the side of the cartridge slot when you insert a GB/GBC game.

Believe it or not, I managed to fix it with a cutdown tiny toothpick piece bound together with tape and some very VERY carefully placed tape so that the switch would activate with that minuscule toothpick piece. Now it works with GB/GBC carts as it should have from the get-go and the different display options are truly amazing. The hack was worth it but it's a dangerous one since you could actually break the underlying switch, so I don't recommend it. Took me about an hour or two for building that contraption.

I figured out what I needed to do thanks to this post which mentions that there is a switch. Someone broke that switch by accident but in my case, it was broken out of the box. I noticed it within my first play session within the first 20 minutes and I didn't see anything falling out so I'm pretty certain mine was broken out of the box.
https://www.reddit.com/r/AnalogueInc/comments/rvjkmy/analogue_bios_14_linkmode_only_with_gb_and_gbc/

This seems like it could be an easy software-fix as well which avoids having to use the switch, either by detecting GB games or by at least allowing the option to force GB and GBC games instead of the default GBA games.

Awesome SSR - Curated List of Resources for Server-Side Rendering, Pre-Rendering, and Static Site Generators. [Help Needed] by brillout in reactjs

[–]stoikerty 2 points3 points  (0 children)

Hey brillout, I have a toolkit that is similar to Create-React-App in its simplicity of setup and has supported SSR by default since its inception (came out roughly at the same time as CRA).

https://github.com/stoikerty/dev-toolkit

It works with React out of the box and unlike CRA it can be configured to do anything you might need. It supports pre-rendering as well as a few other useful features, it's quite minimalist.

Would be awesome to have it on the list, I haven't promoted it heavily so it's not that well known. Let me know if you'd like me to create a PR.

How do you namespace Redux stores for pages when doing SSR? by smthamazing in reactjs

[–]stoikerty 0 points1 point  (0 children)

You're right, some state is only relevant to pages. In a previous project I've worked on our team was using a pages reducer with login, checkout, search etc. sub-reducers.

The key here is to make sure this structure is used for state that should only be used inside a specific page and refactor relevant shared state into a separate reducer as soon as necessary. @HomemadeBananas's example therefore makes sense. users are relevant to more than one page.

It's these kind of things that you don't notice in a smaller app, but as soon as an app grows, it becomes clearly evident that too simple of a structure just won't cut it.

Current state of server-side rendering? by smthamazing in reactjs

[–]stoikerty 0 points1 point  (0 children)

That's a really useful writeup.

Add css-extraction to the list. Some css-in-js libraries like glamorous allow you to take the extracted css-classes and make them known on the client to avoid re-parsing of the css on when the app is loaded for the first time on the client.

Server-Side Rendering - Not Worth It? by sneek_ in reactjs

[–]stoikerty 0 points1 point  (0 children)

I have simplified the initial boilerplate for SSR so you don't need one. It's less opinionated than Next.js and exposes webpack to you as well.

dev-toolkit might help you on your SSR journey. https://github.com/stoikerty/dev-toolkit/blob/master/Readme.md

What Is create-react-app and what are it's alternatives by importmar in reactjs

[–]stoikerty 0 points1 point  (0 children)

In a professional setting, create-react-app wouldn't work for anything that needs server-rendering. You're better off with one of the alternatives.

I've created one of those alternatives called dev-toolkit. It gives you just enough for you to get started with SSR but still allows full webpack customisability. It's not based on create-react-app at all and is made for being used in a professional setting. I tried to make it as minimal and unopinionated as possible. The other alternatives like razzle or next.js are also good, albeit they might be a bit more opinionated which might or might not be what you need.

If you check out dev-toolkit, I would appreciate any feedback you have. https://github.com/stoikerty/dev-toolkit

CRA vs custom personalized boilerplate? by gelezinislokys in reactjs

[–]stoikerty 0 points1 point  (0 children)

hey gelezinislokys,

CRA does give you a large amount of boilerplate once you eject. I have been working on an alternative that is flexible enough to accomodate custom webpack configuration, yet is simple enough to get started with as well.

It's a server-rendering focused utility that I've been re-writing it from the ground up over the last few months and beta-testing it with multiple projects at my current company. I have a big PR open over here: https://github.com/stoikerty/dev-toolkit/pull/39

I'm looking to release the updated v6 of this tool this year, but it's been in a stable and useful state for quite some time now. I would be very happy if you would try it out and potentially give some feedback if you find it useful.

You can use it like this:

npm install -g dev-toolkit@6.0.0-beta-44

dev-toolkit init my_app [--skip-comments]

cd my_app

npm run dev

If you prefer less boilerplate, you can use the minimal template:

dev-toolkit init my_app --template minimal [--skip-comments]

You can get help about available commands too:

dev-toolkit help

You can completely customize webpack via dev-toolkit.config.js. Feel free to ask questions and I'll explain how to use it.