satellite
Next.js
satellite | Next.js | |
---|---|---|
14 | 2,046 | |
6 | 120,804 | |
- | 0.8% | |
8.4 | 10.0 | |
about 2 years ago | 19 minutes ago | |
JavaScript | JavaScript | |
BSD 2-clause "Simplified" 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.
satellite
-
Last piece of the puzzle: Moving Satellite inside Telescope
This week we released Telescope 2.8 and, as part of the new release, we moved the Satellite project inside of the Telescope monorepo. Satellite is the microservice framework used by Telescope.
-
Telescope Sheriff
The issue was caused by a recent PR that changed SECRET to JWT_SECRET (To use with the latest version of Satellite) without adding the required variables in env.staging and env.production.
-
Fixes and documentation
There is an ongoing issue that I am trying to address: moving the Satellite repo inside Telescope to complete the monorepo. I haven't been successful so far, so I will ask other students to collaborate on this one, and maybe it can be done by Release 2.7.
-
Taking Lead in Telescope
The second thing I'd like to note is the last bit of my quote, where I will probably laugh. I can look back now and definitely laugh. Not only did I do my first release, I did my second and third. Being sheriff was overwhelming, I wanted to encourage all our contributors and push them in the right direction, ask if they required support when issues went stale, but also handle new high priority issues.
-
Mid way before release 2.6
A lot happened this week, on Tuesday meeting the sheriff, went through the task to-do for release 2.6, and on Thursday it was a triage of Pull requests and issues. During the triage, I go assigned to more issues, in the area of react native, docker, and a bit of front-end fix. Also, did my first release on an open sources project in Satellite repo.
-
Second week of OSD700
For release 2.6 I have been working on some issues already especially in satellite repo. Issues:
-
Getting up to speed
I opened a PR to solve this issue. I removed most of the file src/backend/lib/redis.js and some packages to fully utilize Redis connection from Satellite. After some back and forth, it got merged but a bit later Duke found out that it broke master, the backend couldn't start.
-
Contributing to Telescope: Wrapping up 0.4
Continuing on from that blog, I ended up creating two more pull requests as I was wrapping up 0.4: #22
-
Working on GoDaddy Terminus
To start, I thought I could solve Telescopes Issue by fixing some code on Telescope or Satellite in order for the CORS errors to stop. I soon learned that the main problem wasn't fixable from our code bases and had to be fixed from Terminus.
-
DPS911 Blog #13: One more step until the finish line
This week, I worked on porting our ElasticSearch client to Satellite. That one was more of a pain in the ass than I thought it would be, mainly because it wasn't starting. Also, intellisense wasn't as strong as it was with Redis, so I had to turn to documentation alot, both for regular and the mock versions of ELS. You can find my PR for that, here.
Next.js
-
How to Build Your Own ChatGPT Clone Using React & AWS Bedrock
Next.js has long cemented itself as one of the front runners in the web framework world for JavaScript/TypeScript projects so we’re going to be using that. More specifically we’re going to be using V14 of Next.js which allows us to use some exciting new features like Server Actions and the App Router.
-
Is purging still the hardest problem in computer science?
Web frameworks like Next.js will usually include this feature, but do check that they set the caching headers correctly!
-
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.
-
A brief history of web development. And why your framework doesn't matter
> It’s important to be aware of what you are getting if you go with React, and what you are getting is a far cry from what a framework would offer, with all the corresponding pros and cons.
Would you like to elaborate on that?
In my experience, with something as great, size/ecosystem-wise as React, there will almost always be at least one "mainstream" package for whatever you might want to do with it, that integrates pretty well. Where a lot of things might come out of the box with a framework, with a library I often find myself just needing to install the "right" package, and from there it's pretty much the same.
For example, using https://angular.io/guide/i18n-overview or installing and using https://react.i18next.com/
Or something like https://angular.io/guide/form-validation out of the box, vs installing and using https://formik.org/
Or perhaps https://angular.io/guide/router vs https://reactrouter.com/en/main
Even adding something that's not there out of the box is pretty much the same, like https://primeng.org/ or https://primereact.org/
React will typically have more fragmentation and therefore also choice, but I don't see those two experiences as that different. Updates and version management/supply chain will inevitably be more of a mess with the library, admittedly.
Now, projects like Next https://nextjs.org/ exist and add what some might regard as the missing pieces and work well if you want something opinionated and with lots of features out of the box, but a lot of those features (like SSR) are actually pretty advanced and not always even necessary.
-
System & Database Design (Day 1) - Creating a SaaS Startup in 30 Days
Next.js: For the website and the admin dashboard
-
Runtime environmental variables in Next.js 14
Until the time of writing, there is no official example of how to enable runtime environmental variables in a Dockerized Next.js app, as utilizing unstable_noStore would only dynamically evaluate variables on the server (node.js runtime). There is also an interesting discussion regarding this topic on GitHub.
-
@matstack/remix-adonisjs VS Next.js - a user suggested alternative
2 projects | 24 Apr 2024
next.js is a very popular React framework. remix-adonisjs includes more functionality through the AdonisJS backend ecosystem, and should be easier to self-host and self-manage.
-
Meet Cheryl Murphy: Full-Stack Developer, lifelong learner, and volunteer Project Team Lead at Web Dev Path
Cheryl Murphy is not only a dedicated full-stack web developer skilled in technologies like React, Next.js, and NestJs but also a community-driven professional who recently took on the role of volunteer project team lead at Web Dev Path. With a dual Bachelor's degree in Computing and Chemical Engineering from Monash University, Cheryl’s journey in tech is marked by a passion for building accessible solutions and a commitment to fostering community within tech.
-
Ensuring Type Safety in Next.js Routing
For more information, check out this issue.
-
Styling Your Site with Next.js and MUI: Creating a Dynamic Theme Switcher
Remember to start the Next.js server with pnpm dev.
What are some alternatives?
telescope - A tool for tracking blogs in orbit around Seneca's open source involvement
vite - Next generation frontend tooling. It's fast!
dateformat - A node.js package for Steven Levithan's excellent dateFormat() function.
Express - Fast, unopinionated, minimalist web framework for node.
compose-middleware - Compose an array of middleware into a single function for use in Express, Connect, router, etc
SvelteKit - web development, streamlined
slirp4netns - User-mode networking for unprivileged network namespaces
MERN - ⛔️ DEPRECATED - Boilerplate for getting started with MERN stack
workspace-images - Ready to use docker images for Gitpod workspaces
Angular - Deliver web apps with confidence 🚀
hes-dead-jim - A command-line tool for finding and reporting dead/broken links in a file or webpage.
fastify - Fast and low overhead web framework, for Node.js