ToolJet
vite
Our great sponsors
ToolJet | vite | |
---|---|---|
174 | 787 | |
26,580 | 64,769 | |
2.2% | 1.8% | |
9.9 | 9.9 | |
4 days ago | about 10 hours ago | |
JavaScript | TypeScript | |
GNU Affero General Public License v3.0 | 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.
ToolJet
- ToolJet: Open-Source Alternative to Retool
-
Launch HN: Creo (YC W24) β Build Internal Tools with React/NextJS
As everyone mentioned, there are tons of OSS alternatives which are well established. One of which is tooljet: https://github.com/ToolJet/ToolJet
- Another open-core project rejecting PR citing paid feature
- Automate complicated manual business processes
- Launch HN: Refine (YC S23) β Open-Source Retool for Enterprise
- ToolJet Secures Funding from Microsoft
-
Open source Retool Alternatives: ILLA Cloud
I discovered ToolJet just yesterday - https://github.com/ToolJet/ToolJet
-
Building a customer Support Desk App with ToolJet and PostgreSQL
ToolJet is an open-source low-code framework that enables us to build full-stack web applications within a few minutes. With ToolJet, you can create standalone fully-functional full-stack applications or embed applications into other websites.
- Budibase, a GUI for building apps on top of SQL, REST, Google Sheets, and open-source alternative to Airtable and Retool, now ships with a π₯ Multiplayer Collaboration, π€ Autocomplete Bindings, π and Synchronous Automations.
- ToolJet 2.6.0 - Open-source low-code framework for building business applications with AI assistant for SQL queries & custom JS/Py code. Also added OpenAI as a plugin, OCR via AWS Textract & gRPC plugin. Deploy using Docker, k8s, AWS AMI & more! Alternative to Retool, Power Apps & Mendix.
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?
appsmith - Platform to build admin panels, internal tools, and dashboards. Integrates with 25+ databases and any API.
Next.js - The React Framework
budibase - Budibase is an open-source low code platform that helps you build internal tools in minutes π
parcel - The zero configuration build tool for the web. π¦π
authentik - The authentication glue you need.
esbuild - An extremely fast bundler for the web
nocodb - π₯ π₯ π₯ Open Source Airtable Alternative
swc - Rust-based platform for the Web
Directus - The Modern Data Stack π° β Directus is an instant REST+GraphQL API and intuitive no-code data collaboration app for any SQL database.
astro - The web framework for content-driven websites. βοΈ Star to support our work!
n8n - Free and source-available fair-code licensed workflow automation tool. Easily automate tasks across different services.
Rollup - Next-generation ES module bundler