jetstream
vite
jetstream | vite | |
---|---|---|
23 | 790 | |
3,885 | 64,769 | |
0.4% | 0.9% | |
8.7 | 9.9 | |
4 days ago | 7 days ago | |
PHP | 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.
jetstream
-
Is using the repository pattern best practise?
For writing models I would suggest using Action Closes. One example of them can be found in Jetstream's sourcecode. Actions are great to test in isolation and link to user stories.
-
Ask HN: What would be your stack if you are building an MVP today?
While I prefer python for everything else, I'd go with Laravel Jetstream[1] for an MVP, just like I did with the last one I had to build. It's laravel, you can use Vue (React or Svelte) for your views instead of the blade templating language that comes with the framework. Jetstream also comes with Auth, user login and subscription and other useful stuff.
And for the flavor, I'd just go with DaisyUI[2] again, since it's based on tailwindcss and it's what I've been using lately.
In my experience, I can build MVPs real fast with the stack described above.
[1] https://jetstream.laravel.com
-
How to call api internally and is that a good idea to call like that?
A well-implemented example of this would be in Laravel Jetstream, where an Actions namespace is defined for performing user-oriented tasks in Laravel Fortify — such as updating the user profile.
- What auth scaffolding should be used with sanctum tokens
- Admin panel with basic html css js
-
`npm run dev` not copying css or js files to public. Bug?
This legacy package is a very simple authentication scaffolding built on the Bootstrap CSS framework. While it continues to work with the latest version of Laravel, you should consider using Laravel Breeze for new projects. Or, for something more robust, consider Laravel Jetstream.
-
Preventing User Enumeration Attack in Laravel Apps
Laravel provide us with robust solutions and starter kits for authentication so let's start by creating a new Laravel 9 project and install Jetstram
- Jetstream - Tailwind scaffolding for the Laravel framework.
- Jetstream – Tailwind scaffolding for the Laravel framework
-
Moving an existing vanilla PHP website to Laravel/Vue, using packages for different components
In terms off bullet points you added, I've made something pretty similar using Laravel with : Laravel Jetstream(application starter kit with inertia + vue stack) https://jetstream.laravel.com/
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?
breeze - Minimal Laravel authentication scaffolding with Blade, Vue, or React + Tailwind.
Next.js - The React Framework
jwt-auth - 🔐 JSON Web Token Authentication for Laravel & Lumen
parcel - The zero configuration build tool for the web. 📦🚀
django-unicorn - The magical reactive component framework for Django ✨
esbuild - An extremely fast bundler for the web
Tailwind CSS - A utility-first CSS framework for rapid UI development.
swc - Rust-based platform for the Web
livewire - A full-stack framework for Laravel that takes the pain out of building dynamic UIs.
astro - The web framework for content-driven websites. ⭐️ Star to support our work!
sanctum - Laravel Sanctum provides a featherweight authentication system for SPAs and simple APIs.
Rollup - Next-generation ES module bundler