Water.css
vite
Our great sponsors
Water.css | vite | |
---|---|---|
33 | 789 | |
8,184 | 64,769 | |
- | 2.1% | |
0.0 | 9.9 | |
3 months ago | 4 days ago | |
CSS | 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.
Water.css
-
Where Is Noether's Principle in Machine Learning?
Thank you!
In the beginning, I used kognise'z water.css [1], so most of the smart decisions (background/text color, margins, line spacing I think) probably come from there. Since then it's been some amount of little adjustments. The font is by Jean François Porchez, called Le Monde Livre Classic [2].
I draft in Obsidian [3] and build the site with a couple python scripts and KaTeX.
[1] https://watercss.kognise.dev/
[2] https://typofonderie.com/fr/fonts/le-monde-livre-classic
[3] https://obsidian.md/
-
Ask HN: Experience Starting a Blog
Thank you!
I must give credit to Kognise though, the style is simply their formidable water.css layout. It saved me a lot of time and anguish when I was about to get my blog started.
https://watercss.kognise.dev/
- CSS for readability
-
No CSS Club – because no JavaScript was not hardcore enough
https://watercss.kognise.dev/ I would argue classless css is the way to go, you just include a single css file, then write your html without touching any css anymore, all related tags in html are inherently css-ed for you. a nice trade off for me sometimes.
- Filenames and Pathnames in Shell: How to Do It Correctly
-
Classless.css – Less Classes. Less Overhead
Like the previous submitter ( https://news.ycombinator.com/item?id=30885700 April 2022 ) I found clasless.css while investigating semantic html-oriented css libraries and this one stood out to me as having a good balance. I'm not ideologically opposed to using classes, but using them for every bit of styling seems off and I'd rather see good default styles for regular semantically structured html. For example, classless.css uses the "card" class for cards which don't have a clear analog in among standard html tags: https://developer.mozilla.org/en-US/docs/Web/HTML/Element
Other libraries:
Water.css: https://watercss.kognise.dev/
MVP.css: https://andybrewer.github.io/mvp/
Missing.css: https://missing.style/
-
Ur Go-To on UI with Flask?
WaterCSS, very basic but good-looking UI in my opinion
- О заметках в markdown файлах
-
Looks great on my machine
Slap this on it and you're good: https://github.com/kognise/water.css/
-
Show HN: Neat, the Minimalist CSS Framework
- https://watercss.kognise.dev/ Small size (< 2kb)
vite
-
Top 12+ Battle-Tested React Boilerplates for 2024
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 vs Nextjs: Which one is right for you?
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.
-
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:
What are some alternatives?
classless-css - A list of classless CSS themes/frameworks with screenshots
Next.js - The React Framework
pico - Minimal CSS Framework for semantic HTML
parcel - The zero configuration build tool for the web. 📦🚀
Rust Language Server - Repository for the Rust Language Server (aka RLS)
esbuild - An extremely fast bundler for the web
reagent - A minimalistic ClojureScript interface to React.js
swc - Rust-based platform for the Web
hyperscript - Create HyperText with JavaScript.
astro - The web framework for content-driven websites. ⭐️ Star to support our work!
prism-themes - A wider selection of Prism themes
Rollup - Next-generation ES module bundler