vite-imagetools
vite
Our great sponsors
vite-imagetools | vite | |
---|---|---|
8 | 787 | |
845 | 64,769 | |
- | 1.8% | |
8.9 | 9.9 | |
3 days ago | about 17 hours ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vite-imagetools
-
how to integrate vite-imagetools into sveltekit 1.0
The first thing is to install vite-imagetools from https://github.com/JonasKruckenberg/imagetools
- Do you know a package that could do that ? POSTCSS ?
-
QWER : Simply Awesome Blog Starter built with SvelteKit and Love
Automatic image optimization via vite-imagetools.
-
Next.js image alternative in Svelte
The closest solution Iโve found is hacking something together yourself with vite-imagetools
-
What are the weirdest CMS you've seen used to host content?
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.
-
From PHP to SvelteKit - scanning directories
#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.
-
Show HN: I hype drivingly recreated my website and it was awesome
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
-
Using vite-imagetools with SvelteKit
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:
vite
-
Setup React Typescript with Vite & ESLint
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') } } })
-
Approaches to Styling React Components, Best Use Cases
I am currently utilizing Vite:
-
Getting started with TiniJS framework
Homepage: https://vitejs.dev/
-
Use CSS Variables to style react components on demand
Without any adding any dependencies you can connect react props to raw css at runtime with nothing but css variables (aka "custom properties"). If you add CSS modules on top you don't have to worry about affecting the global scope so components created in this way can be truly modular and transferrable. I use this with vite.
-
RubyJS-Vite
Little confused as to why it has vite in itโs name, it seems unrelated to https://vitejs.dev/
-
Ask HN: How do we include JavaScript scripts in a browser these days?
it says in their docs that they recommend Vite https://vitejs.dev/
it goes like this.
1. you create a repo folder, you cd into it.
2. you create a client template using vite which can be plain typescript, or uses frameworks such as react or vue, at https://vitejs.dev/guide/
3. you cd in that client directory, you npm install, then you npm run dev, it should show you that it works at localhost:5173
4. you follow the instructions on your url, you do npm install @web3modal/wagmi @wagmi/core @wagmi/connectors viem
5. you follow the further instructions.
> It seems like this is for npm or yarn to pull from a remote repository maintained by @wagmi for instance. But then what?
you install the wagmi modules, then you import them in your js code, those code can run upon being loaded or upon user actions such as button clicks
> Do I just symlink to the node_modules directory somehow? Use browserify? Or these days I'd use webpack or whatever the cool kids are using these days?
no need for those. browserify is old school way of transpiling commonjs modules into browser-compatible modules. webpack is similar. vite replaces both webpack and browserify. vite also uses esbuild and swc under the hood which replaces babel.
> I totally get how node package management works ... for NODE. But all these client-side JS projects these days have docs that are clearly for the client-side but the ES2015 module examples they show seem to leave out all instructions for how to actually get the files there, as if it's obvious.
pretty much similar actually. except on client-side, you have src and dist folders. when you run "npm run build" vite will compile the src dir into dist dir. the outputs are the static files that you can serve with any http server such as npx serve, or caddy, or anything really.
> What gives? And finally, what exactly does "browserify" do these days, since I think Node supports both ES modules and and CJS modules? I also see sometimes UMD universal modules
vite supports both ecmascript modules and commonjs modules. but these days you'll just want to stick with ecmascript which makes your code consistently use import and export syntax, and you get the extra benefit of it working well with your vscode intellisense.
> In short, I'm a bit confused how to use package management properly with browsers in 2024: https://modern-web.dev/guides/going-buildless/es-modules/
if people want plain js there is unpkg.com and esm.sh way, but the vite route is the best for you as it's recommended and tested by the providers of your modules.
> And finally, if you answer this, can you spare a word about typescript? Do we still need to use Babel and Webpack together to transpile it to JS, and minify and tree-shake, or what?
I recommend typescript, as it gives you better type-safety and better intellisense, but it really depends. If you're new to it, it can slow you down at first. But as your project grows you'll eventually see the value of it. In vite there are options to scaffold your project in pure js or ts.
-
Deploy a react projects that are inside a subdirectories to GitHub Pages using GitHub Actions (CI/CD)
First you have to know that all those react projects are created using Vite, and for each of them, you need change the vite.config.ts file by adding the following configuration:
-
CSS Hooks and the state of CSS-in-JS
CSSHooks works with React, Prereact, Solid.js, and Qwik, and weโre going to use Vite with the React configuration. First, let's create a project called css-hooks and install Vite:
-
Collab Lab #66 Recap
JavaScript React Flowbite Tailwind Firebase - Auth, Database, and Hosting Vite
-
Use React.js with Laravel. Build a Tasklist app
For this full-stack single-page app, you'll use Vite.js as your frontend build tool and the react-beautiful-dnd package for draggable items.
What are some alternatives?
vike - ๐จ Like Next.js / Nuxt but as do-one-thing-do-it-well Vite plugin.
Next.js - The React Framework
unplugin-vue-components - ๐ฒ On-demand components auto importing for Vue
parcel - The zero configuration build tool for the web. ๐ฆ๐
js-image-carver - ๐ Content-aware image resizer and object remover based on Seam Carving algorithm
esbuild - An extremely fast bundler for the web
vite-aliases - Alias auto generation for Vite
swc - Rust-based platform for the Web
vite-plugin-inline-css-modules - Write CSS modules without leaving your javascript!
astro - The web framework for content-driven websites. โญ๏ธ Star to support our work!
vite-plugin-rsw - ๐ฆ wasm-pack plugin for Vite
Rollup - Next-generation ES module bundler