dotfiles-public VS vite

if you are using cmp and lspkind, look at this awesome guy's cmp config

ps: If you want a more in depth setup check this repo , from here I learned how to use vim and I felt quite comfortable with the configuration changing the color scheme and little else

Craftzdog's Neovim Config

Some of my dotfiles follow/use/clone dotfiles from https://github.com/craftzdog/dotfiles-public

For more context, I'm basically using a copy of nvim config

For some reason, it does not help me with the syntax, it only helps me with what I have already used in the code. I use the well-known Devaslife config (https://github.com/craftzdog/dotfiles-public). Why would this happen?

I hope that gives you some directions. Also, look at "https://github.com/craftzdog/dotfiles-public" for more ideas.

You can find my Neovim configuration here. It's just a fork of craftzdog's configuration.

Huge thanks to this repo and this vedio

As of this writing, initializing a Hattip project requires some manual commands. However, keep in mind that a zero-config development environment based on Vite is in the works.

import { defineConfig } from 'vite' import react from '@vitejs/plugin-react' // https://vitejs.dev/config/ export default defineConfig({ plugins: [react()], server: { port: 4200, } })

For the frontend of "I Disappear," I leverage the automated build & deploy system provided by Netlify, which seamlessly integrates with Vite. This setup ensures that every deployment is optimized for performance, utilizing Vite’s modern build tools to enhance speed and efficiency.

Given our team's collective proficiency within the React ecosystem, we decided to leverage this expertise for our project. Initially, we contemplated utilizing Next.js; however, due to the limited practical experience with this technology among key engineers and the pressing timeline to develop the first prototype, we opted for a Single Page Application(SPA) approach. For bundling, we selected Vite, primarily due to its super fast build times, simplicity of configuration, and potential for a nearly seamless transition to server-side rendering.

We are continuing to add new project templates for various types of projects, and we've recently created one for the infamous combination of React with Vite tooling.

Vite focuses on providing an extremely fast development server and workflow speed in web development. It uses its own ES module imports during development, speeding up the startup time.

Vite and Next.js are both top 5 modern development framework right now. They are both great depending on your use case so we’ll discuss 4 areas: Architecture, main features, developer experience and production readiness. After learning about these we’ll have a better idea of which one is best for your project.

import { defineConfig } from 'vite' import react from '@vitejs/plugin-react-swc' import path from 'path' // https://vitejs.dev/config/ export default defineConfig({ plugins: [react()], server: { port: 3000 }, css: { devSourcemap: true }, resolve: { alias: { '~': path.resolve(__dirname, './src') } } })

I am currently utilizing Vite:

Homepage: https://vitejs.dev/