JSONFeed VS vite

If you have a web feed, be it RSS or Atom or JSON Feed, help others discover it!

Imagine you have an RSS feed similar to this. The objective is to obtain that RSS feed, analyze the data it contains, and take action with it. RSS is an XML format, whereas JSON is arguably easier to work with than XML. While many APIs provide JSON results, RSS is less likely to receive them, despite their existence.

At least for now, Astro clearly falls short in this category. Its built-in ability to provide RSS feeds is rather limited, and it doesn’t yet enable JSON feeds at all.5 In the meantime, some users, including Yours Truly, have gotten around this by using the third-party feed package, which supports RSS and JSON feeds.6

want to also support JSON Feed?

-------- # Metadata comes from _data/metadata.json permalink: "{{ metadata.jsonfeed.path | url }}" eleventyExcludeFromCollections: true -------- { "version": "https://jsonfeed.org/version/1", "title": "{{ metadata.title }}", "home_page_url": "{{ metadata.url }}", "feed_url": "{{ metadata.jsonfeed.url }}", "description": "{{ metadata.description }}", "author": { "name": "{{ metadata.author.name }}", "url": "{{ metadata.author.url }}" }, "items": [ {%- for post in collections.posts | reverse %} {%- set absolutePostUrl %}{{ post.url | url | absoluteUrl(metadata.url) }}{% endset -%} { "id": "{{ absolutePostUrl }}", "url": "{{ absolutePostUrl }}", "title": "{{ post.data.title }}", "tags": [ {%- for tag in helpers.removeCollectionTags(post.data.tags) -%} "{{tag}}" {%- if not loop.last %}, {%- endif %} {%- endfor %}], "summary": "{{ post.data.description }}", "content_html": {% if post.templateContent %}{{ post.templateContent | dump | safe }}{% else %}""{% endif %}, "date_published": "{{ post.date | rssDate }}" } {%- if not loop.last -%} , {%- endif -%} {%- endfor %} ] }

Your wish is my command.

For the frontend of "I Disappear," I leverage the automated build & deploy system provided by Netlify, which seamlessly integrates with Vite. This setup ensures that every deployment is optimized for performance, utilizing Vite’s modern build tools to enhance speed and efficiency.

Given our team's collective proficiency within the React ecosystem, we decided to leverage this expertise for our project. Initially, we contemplated utilizing Next.js; however, due to the limited practical experience with this technology among key engineers and the pressing timeline to develop the first prototype, we opted for a Single Page Application(SPA) approach. For bundling, we selected Vite, primarily due to its super fast build times, simplicity of configuration, and potential for a nearly seamless transition to server-side rendering.

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.

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 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.

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') } } })

I am currently utilizing Vite:

Homepage: https://vitejs.dev/

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.

Little confused as to why it has vite in it‘s name, it seems unrelated to https://vitejs.dev/