sidewinder
vite
sidewinder | vite | |
---|---|---|
15 | 790 | |
163 | 64,769 | |
- | 0.9% | |
7.6 | 9.9 | |
5 days ago | 6 days ago | |
Python | 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.
sidewinder
-
Sidewinder: Configured Django on your own server in 10 minutes
7 months ago I posted here about my open source starter kit Sidewinder https://github.com/stribny/sidewinder. The goal was to create a kit that would come prepared with development and deployment tools, mainly to deploy a Django app to a single private virtual server.
-
Django Allauth: Do I have to style all the templates?
You can have a look at https://github.com/stribny/sidewinder where I styled the most important pages (https://github.com/stribny/sidewinder/tree/master/templates/account) for email-based login (no social login).
-
How do you test JS code and features that handle monetary transactions?
If you are talking about end-to-end UI tests, then using Playwright you can write your tests in Python and execute them together with other tests that you run with pytest. I have exactly this in https://stribny.github.io/sidewinder/ starter kit.
-
Are there any open source comprehensive SaaS templates in django?
You should probably really define what you need a bit better. I have a starter kit (https://stribny.github.io/sidewinder/) that has some good defaults out of the box (like using django-allauth). Pair it with e.g. https://github.com/paddle-python/dj-paddle for Paddle (or something similar for Stripe) and you have a good base.
-
How to deploy Django to a Virtual Maschine?
Feel free to check my Ansible playbook (`deployment`) folder of my starter kit: https://stribny.github.io/sidewinder/
-
Django is truly amazing
You can see it working in a Django project here: https://stribny.github.io/sidewinder/
- I made a Django starter kit that can be deployed easily
-
Sunday Daily Thread: What's everyone working on this week?
Check out https://stribny.github.io/sidewinder/, maybe that's what you next project will need :D
-
Ask HN: What would be your stack if you are building an MVP today?
My first choice if the product is a good fit would be old school Django deployed to a single VPS (no docker). I am creating a public starter kit that does exactly that, including the deployment part: https://stribny.github.io/sidewinder/
However, there are lots of use cases that would call for additional SPA (Vue/Nuxt), or other tech. So in that case I'd add it or replace the tech stack entirely. I'd probably avoid specialized cloud services, might consider something like https://supabase.com tho if the app doesn't need a complex backend.
- Sidewinder: open source Django starter kit that focuses on good defaults, developer experience, and deployment
vite
-
Inflight Magazine no. 9
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.
-
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:
What are some alternatives?
api - Promise and RxJS APIs around Polkadot and Substrate based chains via RPC calls. It is dynamically generated based on what the Substrate runtime provides in terms of metadata.
Next.js - The React Framework
atrilabs-engine - 🧘♂️ Open-source no-code & code web app builder
parcel - The zero configuration build tool for the web. 📦🚀
typeconv - Convert between JSON Schema, TypeScript, GraphQL, Open API and SureType
esbuild - An extremely fast bundler for the web
activepieces - Your friendliest open source all-in-one automation tool ✨ Workflow automation tool 100+ integration / Enterprise automation tool / Zapier Alternative
swc - Rust-based platform for the Web
music-demixing-challenge-starter-kit - Starter kit for getting started in the Music Demixing Challenge.
astro - The web framework for content-driven websites. ⭐️ Star to support our work!
cherry - Minimalistic macOS CLI Pomodoro Timer
Rollup - Next-generation ES module bundler