vite-imagetools VS vercel

The first thing is to install vite-imagetools from https://github.com/JonasKruckenberg/imagetools

Automatic image optimization via vite-imagetools.

The closest solution I’ve found is hacking something together yourself with vite-imagetools

The projects this solutions works with are customised Sveltekit projects I made. It has everything: markdown parser using Mdsvex, image converting tool using vite-imagetools, it has toml parser, and of course live preview and lots of other smaller things like markdown directives.

#2 - I'm not sure about the performance and/or resource usage implication around importing over 100 images like this. Would all of these images get bundled and included in the production build? The upside here is that something like vite-imagetools could be used if/when needed.

Hello HN,

I had some christmas free time over the last two weeks (Merry Christmas btw ;-)) and used that time to completely recreate the website of my app[1]. I used all the fancy new tools. I didn't know some of them when I started.

What was my goal?

* Pretty website

* Blazing fast

* Mobile first

* SSR

* Webp support

* Generally all the best website practices (high lighthouse score)

What did I use?

* Tailwindcss (https://tailwindcss.com/)

* Tailwind Components (https://tailwindui.com/)

* React (https://reactjs.org/)

* ViteJs (https://vitejs.dev/)

* Kubernetes (https://kubernetes.io/)

Well what can I say. I hate creating websites, but this was an awesome experience. Never have I created a website more efficiently. Tailwindcss + Components is just the best. ViteJS is so so so much easier to setup compared to webpack and has SSR support on top of it. React has been around somewhat longer and I did a lot of projects with it, so that was a nobrainer. Special thanks to all the people who created these awesome tools.

PS: If you work with lots of images, do yourself a favor and use something like https://github.com/JonasKruckenberg/imagetools. It saved me hours of dreadful work.

[1] https://stockevents.app

Spent the better part of today attempting to find a working alternative to svelte-images, which I had been using in Sapper, but found was not working in SvelteKit. Was referred to [vite-imagetools](https://github.com/JonasKruckenberg/vite-imagetools) on discord, which is a vite plugin that dynamically import and transform images (srcset). Here are the steps required to integrate vite-imagetools with SvelteKit:

Choosing Vercel was a natural decision as it has become the default method for launching apps that are accessible to a wide audience. The simplicity of configuring environment variables, domains, and other settings facilitated this choice. We have implemented feature branch deployment to guarantee that the code is operational and prepared for peer review.

Next, we'll deploy our ecommerce website to Vercel (which is a great choice to host your Next.js website). Other hosting options include Netlify and Render.

This approach has seen a proliferation of platforms that offer this as a service(Netlify, Vercel, Cloudflare etc.) and also a proliferation of frameworks with different strengths and weaknesses(list of frameworks supported cloudflare).

Next.js: Highly optimized for production from the start, with features tailored for performance in real-world scenarios, including extensive support for SEO and server-side capabilities. Note: With deployment to Vercel is free and comes with additional free tooling such as website analytics and more.

Easily deploy your Next.js app with Vercel by clicking the button below:

Now go to https://vercel.com, sign up for an account, and click "New Project". Connect your GitHub account and give Vercel permission to access your repositories.

Next.js has become a standard choice for developing React applications, offering various deployment options across different platforms. While Vercel is a popular choice for building and deployment, specific project requirements may require deployment to GitLab. In this guide, I'll illustrate the process of deploying a Next.js application to GitLab Pages.

I hosted my portfolio in Vercel. The main reason why I chose it is the hosting has great support for NextJS and IMPORTANT THING, it is total FREE 🤑 (with my usage). And I have use GitHub Action for deploy it automatically when I make or merge change into main branch.

To do this just head over to Vercel and log in if you're not already logged in. If this is your first project, you'll be seeing something like this.

function getContentSecurityPolicyHeaderValue( nonce: string, reportUri: string, ): string { // Default CSP for Next.js const contentSecurityPolicyDirective = { 'base-uri': [`'self'`], 'default-src': [`'none'`], 'frame-ancestors': [`'none'`], 'font-src': [`'self'`], 'form-action': [`'self'`], 'frame-src': [`'self'`], 'connect-src': [`'self'`], 'img-src': [`'self'`], 'manifest-src': [`'self'`], 'object-src': [`'none'`], 'report-uri': [reportUri], // for old browsers like Firefox 'report-to': ['csp'], // for modern browsers like Chrome 'script-src': [ `'nonce-${nonce}'`, `'strict-dynamic'`, // force hashes and nonces over domain host lists ], 'style-src': [`'self'`], } if (process.env.NODE_ENV === 'development') { // Webpack use eval() in development mode for automatic JS reloading contentSecurityPolicyDirective['script-src'].push(`'unsafe-eval'`) } if (process.env.NEXT_PUBLIC_VERCEL_ENV === 'preview') { contentSecurityPolicyDirective['connect-src'].push('https://vercel.live') contentSecurityPolicyDirective['connect-src'].push('wss://*.pusher.com') contentSecurityPolicyDirective['img-src'].push('https://vercel.com') contentSecurityPolicyDirective['font-src'].push('https://vercel.live') contentSecurityPolicyDirective['frame-src'].push('https://vercel.live') contentSecurityPolicyDirective['style-src'].push('https://vercel.live') } return Object.entries(contentSecurityPolicyDirective) .map(([key, value]) => `${key} ${value.join(' ')}`) .join('; ') }