#nextjs

Hey Tumblr, especially LADS' community.. I made something for my personal usage and I realized it might be helpful for other players too. So I think I should share it with the community. TLDR I want to share it with people to see if it is smt that is needed to people? so in a nutshell it is a fan-made guide website focused on LADS companion mechanics! Currently featuring Rafayel's 6 companions (Abysswalker, GOT, LSG, Artist, FP, POTS) with more planned based on feedback. You can visit and check it out on Vercel Key features: - three languages EN/JA/RU - each guide has Protocore, Skill&Weapon, Playgame sections - important terms have pop-up bubbles with explanations - Works on phone, tablet, desktop To see more detailed technical explanation you can visit Project's Github Repo When I started playing last year, I struggled to find detailed companion guides online. Other games have dedicated fan sites, so I thought... why not make one for LADS? This started as my coding practice project, but I realized it might actually help other hunters!

I'd love to hear what other people think but please be kind and respectful when leaving any comments. Down below I attached some GIFs of the project itself.

Trojanised Next.js repositories are targeting developers via build-time scripts and VS Code tasks, establishing stealthy command-and-control channels.

Source: Microsoft

So I did a lot of work on the site in the past few days, and it is looking good. I got the home page finally working. You can see I have a moving home banner and the grid tiles for a hub of links.

Multiple Device Support

I have started the fun/annoying/hard work on adding mobile and 4K support to this project.

When you start adding multiple devices to worry about, you also have to rework the original design of a project. Which is what I had to do. I reworked a lot of the entry pages and stuff to keep their old look while making it dynamic with phones and 4K monitors.

Here is one example: (The wide boy, also icon didn't load in time for the mobile view)

I am getting closer to getting this thing "finished."

So far I have done some smaller phones, 720p monitors, 1080p monitors and 4K monitors. Still need to add tablet and larger phone support.

Before I go, let me leave you with my first thought when I was the screen shot for the Untethered Edge Hood.

Time to spend another Sunday afternoon coding! I'm doing some more work on a NextJS migration of the RPThreadTracker app; today we're figuring out more of the auth flow. Come hang out and say hi, bring some questions, or just chill and chat!

I offer free software development tutoring for new devs and pro-bono web development services for organizations working for progressive change. Visit http://www.blackjack-software.com/about for more information or ask me about it in my Twitch chat!

✧*6/28/2023*✧

finally added a much wanted feature to my todo app! ( ◡̀_◡́)ᕤ

!!!saving tasks in local storage!!!

⁽ᴵ ᵃˡˢᵒ ᵃᵈᵈᵉᵈ ᵃⁿ ᵃᵈᵈ ᵗᵃˢᵏ ᵇᵘᵗᵗᵒⁿ ᵇᵘᵗ ᵗʰᵃᵗˢ ⁿᵒᵗ ᵃˢ ⁱᵐᵖᵒʳᵗᵃⁿᵗ⁾

so when you refresh or close the page and come back to it your tasks still stay there wooooo ৻( •̀ ᗜ •́ ৻)

it still looks absolutely terrible but its one step forward!!

next steps/future features:

✧ delete task button ✧ rearrange tasks

. • ☆ . ° .• °:. *₊ ° . ☆ . • ☆ . ° .• °:. *₊ ° . ☆ . • ☆ . ° .• °:. *₊ ° . ☆

So my last post was about setting up my back-end using Node.js and Sequelize. After setting everything up it was time to create needed routes and queries. I didn't look too much into how to do it, just made an api folder, made a .ts file for every table I have in my database and filled it with CRUD operations + whatever additional query was needed.

After writing all of this I wondered how do I define links for all of these operations? Well as it turns out, when you put files in an api folder in Next.js, they generate by themself, meaning all of my crud operations were now under the same /api/file_table_name link. Obviously that's bad news. It took me 2 days of rearranging (it wasn't hard, just boring XD) and I got this structure

(This is not an entire structure, just a snippet because the whole structure is kinda big and pointless for demonstration)

So now for getting host/api/tag we have an index.ts file which carries the createTag function which requires just a body that contains new tagName.

For host/api/tag/id we have the [id].ts which carries getTagById and DeleteTag function. Now how do we differentiate between those two operations when they are on the same link?

At the end of your file you should have a handler function for which you write the cases in which certain operation happen. In this case it only depends on the http method, but it is possible to add other cases such as potential query string (the on that start with ? in the link ex. api/posts?sort=asc). Here's the code example from my /stickerpack/[id].ts file

So this means the link is going to be host/api/stickerpack/id?type="".

What surprised me was that you don't fetch id with req.params.id, but you fetch everything with req.query, and Next.js I guess just figures out what is a parameter and what is not based on the file name. Another surprising thing is the obvious "id as any" situation XD. It did not work any other way. No idea why. I'll look it up when I get the energy.

Modeled after this tutorial by Web Dev Simplified, but using Next.js and Tailwind

I think following a plain react tutorial while using next js is what gave me some issues, especially being my first react project. I probably should have learned some basic react first before going into frameworks, but oh well.

Trying to line up the text with the CSS paper was a huge pain. I still don't like how it looks but at least it's not floating through the lines anymore lol.

The data persistence gave me the most trouble (took me like FIVE hours 😭). The way it was done in the video did not work for me at all, so I had to figure it out. Local storage can't be accessed during server-side rendering, so accessing localStorage has to be done during client-side rendering, using the useEffect hook. But, as I've learned, the useEffect hook doesn't have a return value, and hooks can only be called at the top level. Then I found out that React intentionally calls useEffect twice and that was resetting my local storage with the empty initialization value -_- But in the end i got it working :)

I built a social app please try it :)