mx-division-builds VS Gridsome

The Mx Builder has just been updated to include the Skill slots!

This app is not meant for making detailed builds. You should use mxswat/mx-division-builds for that purpose.

Believe this comes from the division 2 build tool.

Spreadsheet link: https://docs.google.com/spreadsheets/d/1t2fnQ1NMqFcAmudVlATemOfKZJgrNLrnu4_ZCJBH6A8/edit?usp=sharing mxswat's site: https://mxswat.github.io/mx-division-builds/#/ mxswat's repo (where spreadsheet data have been gathered): https://github.com/mxswat/mx-division-builds

That's a Vue application. I don't know much at all about how Vue works, but it seems like this is the index.html and this is the most important JS file.

GIT: https://github.com/mxswat/mx-division-builds

I use the Division 2 build tool here: https://mxswat.github.io/mx-division-builds

Is there a way to list all items in my stash? Extract it in a csv format directly with some kind of an API. Its actually a nightmare to remember everything you have, I have all my characters full along with my stash and mailbox. We have a nice site to calculate builds, github build. I really don't mind inserting all the items. I tried to do an excel/Google sheets but failed as the formulas were getting really ridiculous.

Is there a way to have the list of my stash exported in a csv foramt? If not is there a site where I can list it manually? By this I mean inputting each item manually to have a visibility of all the items. Yes I'm willing to put all items (300+150x4+100x4). Like this one 'https://mxswat.github.io/mx-division-builds' helps in builds, something similar.

I've been playing for a few days now and just hit wt3. I think I am beginning to understand the build system now. So I've been playing around with the build planner a bit (https://mxswat.github.io/mx-division-builds) and trying to come up with something. My goal is a demolotionist with an AR, dealing damage and not dying all the time. I'm mainly playing in a team of 3. However I'd like a few pointers for the following points:

Thanks for reading!

The web tech stack is actually one of my biggest regrets. It's a static site generator called Gridsome[0] that the maintainers abandoned about three months after I used it to launch the TinyPilot website.

At the time I made the TinyPilot site, I was very excited about Vue, so a Vue-based SSG seemed great. Since then, I've come to find SPAs and most frontend frameworks to be way too much complexity, so I've moved away from Vue, but the TinyPilot website is still stuck on Vue 2.x and bootstrap-vue (which is tied to Vue 2 and Bootstrap 4).

So, it keeps creaking along, but building the 100ish pages on the site takes about five minutes, whereas I think something like Hugo could probably do it in a few seconds. Plus, we get random runtime errors[1] that are pretty hard to debug.

[0] https://gridsome.org/

[1] https://github.com/nuxt/nuxt/issues/5800

Nuxt.js and Gridsome are tailor-made for Vue.js developers.

Gridsome — Jamstack SSG tool for Vue developers

Node is basically back-end Javascript. While powerful alone, almost exclusively you will use a back-end framework like Next.js or Gatsby when using React, and then maybe Nuxt or Gridsome in Vue.

Among other thoughts, I considered a possibility of migration to a newer tech stack (because I can). Don't get me wrong, I actually love Gridsome (which is underneath my website now). But it's quite obsolete, and it's actually a dead project now.

One downside of Gridsome is that development seems to have stopped if you look at their github. For that reason I've recently switched my Gridsome clients to Nuxt

I definitely think Nuxt is worth learning for more than just a static site. However, there is a Gatsby-like Vue framework that focuses on SSG: https://gridsome.org/

Gridsome

All the Static Site Generators have been in the market for many years. With time, they get new improvements and upgrades as well. While considering SSG frameworks, like Gatsby, Nuxt, Gridsome, Next, and many more have been on the developer’s list for a long time. But when we talk about blazing fast web performance as per core web vital, then we have to do a lot of work in the available frameworks, after connecting a lot of dots (in terms of web performance), but still, we cannot achieve the web performance as per our need if we consider a use case of a large website where 20+ components are in one page.