malinajs
turbo
Our great sponsors
malinajs | turbo | |
---|---|---|
3 | 57 | |
1,127 | 24,847 | |
0.6% | 2.1% | |
7.3 | 9.9 | |
2 months ago | 6 days ago | |
JavaScript | Rust | |
MIT License | Mozilla Public License 2.0 |
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.
malinajs
- Malina.js – Front end compiler, inspired by Svelte
-
Electron Adventures: Episode 68: Malina Hex Editor
The other difference is one of many bugs in Malina I discovered. We'd like to do {:else} , but HTML entities do not work properly in Malina in if/else blocks.
-
What are the best alternatives to Svelte?
I think SolidJS or Vue is a correct answer, also https://github.com/malinajs/malinajs is very similar to Svelte, but differs in how it handles reactivity if I remember correctly. Anyway, I would like to offer a different one.
turbo
-
Supermemory - ChatGPT for your bookmarks
Supermemory has three main modules, managed by turborepo:
-
Next.js Shopify eCommerce Starter with Perfect Web Vitals 🚀
From a structural viewpoint, we use a monorepo (Turborepo) to manage packages, even though we currently have only one Next.js app. We chose this setup because it prepares us for future developments, which will include additional apps. This arrangement helps keep the packages well-separated and self-contained.
-
dev.to wrapped 2023 🎁
# src Dockerfile: https://github.com/vercel/turbo/blob/main/examples/with-docker/apps/web/Dockerfile FROM node:18-alpine AS alpine # setup pnpm on the alpine base FROM alpine as base ENV PNPM_HOME="/pnpm" ENV PATH="$PNPM_HOME:$PATH" RUN corepack enable RUN pnpm install turbo --global FROM base AS builder # Check https://github.com/nodejs/docker-node/tree/b4117f9333da4138b03a546ec926ef50a31506c3#nodealpine to understand why libc6-compat might be needed. RUN apk add --no-cache libc6-compat RUN apk update # Set working directory WORKDIR /app COPY . . RUN turbo prune --scope=web --docker # Add lockfile and package.json's of isolated subworkspace FROM base AS installer RUN apk add --no-cache libc6-compat RUN apk update WORKDIR /app # First install the dependencies (as they change less often) COPY .gitignore .gitignore COPY --from=builder /app/out/json/ . COPY --from=builder /app/out/pnpm-lock.yaml ./pnpm-lock.yaml COPY --from=builder /app/out/pnpm-workspace.yaml ./pnpm-workspace.yaml RUN pnpm install # Build the project COPY --from=builder /app/out/full/ . COPY turbo.json turbo.json RUN turbo run build --filter=web # use alpine as the thinest image FROM alpine AS runner WORKDIR /app # Don't run production as root RUN addgroup --system --gid 1001 nodejs RUN adduser --system --uid 1001 nextjs USER nextjs COPY --from=installer /app/apps/web/next.config.js . COPY --from=installer /app/apps/web/package.json . # Automatically leverage output traces to reduce image size # https://nextjs.org/docs/advanced-features/output-file-tracing COPY --from=installer --chown=nextjs:nodejs /app/apps/web/.next/standalone ./ COPY --from=installer --chown=nextjs:nodejs /app/apps/web/.next/static ./apps/web/.next/static COPY --from=installer --chown=nextjs:nodejs /app/apps/web/public ./apps/web/public CMD node apps/web/server.js
-
.dockerignore being ignored by docker-compose? no space left on device
Following this example: https://github.com/vercel/turbo/tree/main/examples/with-docker/apps/web. Except I'm using pnpm. Edit Reddit Codeblocks are horrible and keeps removing all formatting.
-
How to Win Any Hackathon 🚀🤑
The Dockerfile might seem a bit complicated (it is), but the reason for that is mostly just turborepo and the need for good caching. Realistically, you will only need to change the last line, if at all. It is based on this awesome Github Issue.
-
PURISTA: Build with rimraf, esbuild, Turbo & git-cliff
PURISTA is organized in a monorepo. During the development and build process, Turbo is used to execute different tasks and steps on multiple packages with one command.
-
How I approach and structure Enterprise frontend applications after 4 years of using Next.js
Turbo repo
-
Vercel Integration and Next.js App Router Support
Previously we mapped each Vercel project to a single Supabase project. With this release, we're introducing the concept of project 'Connections'. Supabase projects can have an unlimited number of Vercel Connections. This is especially useful for monorepos using Turborepo.
-
How Turborepo is porting from Go to Rust
One detail I enjoy from this post is that sometimes you can just call a CLI[0]. It's easy to spend a lot of time figuring out how to expose some Rust/C code as a library for your language, but I like the simplicity of just compiling, shipping the binary and then calling it as a subprocess.
Yes, there's overhead in starting a new process to "just call a function", but I think this approach is still underutilized.
[0]: https://github.com/vercel/turbo/blob/c0ee0dea7388d1081512c93...
- App Router example repos
What are some alternatives?
Stimulus - A modest JavaScript framework for the HTML you already have
esbuild - An extremely fast bundler for the web
Svelte - Cybernetically enhanced web apps
htmx - </> htmx - high power tools for HTML
turbo - The speed of a single-page web application without having to write any JavaScript
create-t3-app - The best way to start a full-stack, typesafe Next.js app
parcel - The zero configuration build tool for the web. 📦🚀
buck2 - Build system, successor to Buck
Turbolinks - Turbolinks makes navigating your web application faster
nx - Smart Monorepos · Fast CI
qwik - Instant-loading web apps, without effort
morphdom - Fast and lightweight DOM diffing/patching (no virtual DOM needed)