- v17.6Latest
- v17.5
- v17.4
- v17.3
- v17.2
- v17.1
- v17.0
- v16.9
- v16.8
- v16.7
- v16.6
- v16.5
- v16.4
- v16.3
- v16.2
- v16.1
- v16.0
- v15.8
- v15.7
- v15.6
- v15.5
- v15.4
- v15.3
- v15.2
- v15.1
- v15.0
- v14.9
- v14.8
- v14.7
- v14.6
- v14.5
- v14.4
- v14.3
- 14.2
- v14.1
- v14.0
- v13.9
- v13.8
- v13.7
- v13.6
- v13.5
- v13.4
- v13.3
- v13.2
- v13.1
- v13.0
- v12.9
- v12.8
- v12.7
- v12.6
- v12.5
- v12.4
- v12.3
- v12.2
- v12.1
- v12.0
- v11.9
- v11.8
- v11.7
- v11.6
- v11.5
- v11.4
- v11.3
- v11.2
- v11.1
- v11.0
- v10.9
- v10.8
- v10.7
- v10.6
- v10.5
- v10.4
- v10.3
- v10.2
- v10.1
- v10.0
- v9.9
- v9.8
- v9.7
- v9.6
- v9.5
- 9.4
- v9.3
- v9.2
- v9.1
- v9.0
- v8.9
- v8.8
- v8.7
- v8.6
- v8.5
- v8.4
- v8.3
- v8.2
- v8.1
- v8.0
- v7.9
- v7.8
- v7.7
- v7.6
- v7.5
- v7.4
- v7.3
- v7.2
- v7.1
- v7.0
- v6.9
- v6.8
- v6.7
- v6.6
- v6.5
- v6.4
- v6.3
- v6.2
- v6.1
- v6.0
- v5.9
- v5.8
- v5.7
- v5.6
- v5.5
- v5.4
- v5.3
- v5.2
- v5.1
- v5.0
- v4.9
- v4.8
- v4.7
- v4.6
- v4.5
- v4.4
- v4.3
- v4.2
- v4.1
- v4.0
- v3.9
- v3.8
- v3.7
- v3.6
- v3.5
- v3.4
- v3.3
- v3.2
- v3.1
- v3.0
- v2.9
- v2.8
- v2.7
- v2.6
- v2.5
- v2.4
- v2.3
- v2.2
- v2.1
- v2.0
- v1.9
- v1.8
- v1.7
- v1.6
- v1.5
- v1.4
- v1.3
- v1.2
- v1.1
- v1.0
faster_react
It is a complete framework, with automatic compilation of components for the
client side, Server Side Rendering, Hydration and interactive client-side
components. It has folders in its structure for automatic inclusion of pages,
routes, components and static files. It has automatic reload client side and
compilation when "dev":true
in options.json
. There is also automatic
generation of routes based on the file and folder structure. It focuses on
performance and practicality. About Faster, it is an optimized server
middleware. See more at: https://github.com/hviana/faster
Contents
Framework structure
It is important to note that any file modified or created in these directories
will cause the application to compile everything. After this, the application
will be made available to the client side and the browser page will
automatically refresh (when "dev":true
in options.json
). Even routes are
updated dynamically. In these directories, you can organize the files into
subdirectories. Each file must have a export default
. When creating a new
project, sample files already exist.
components folder
Folder of React components/functions that will be interactive on the client
side. Supports .ts
and .tsx
extensions.
pages folder
Pages that will be rendered on the server side and hydrated on the client side.
The page contains a path that matches the directory structure, omitting its
extension. For example, the path localhost:8080/pages/cart
refers to the file
pages/cart.tsx
. It is important to note that the initial route will point to
/pages/index.tsx
(ex: localhost:8080
=> /pages/index.tsx
). Form or JSON
data in post methods, URL parameters (e.g. mypath?param1=a
), and "framework"
data in options.json
will be passed as properties to the React
component/function on the page (in addition to your custom parameters). The
request headers are also passed inside the headers
entry in the React
Function/Component props. Supports .ts
and .tsx
extensions.
api folder
API Routes made with Faster. Supports .ts
extension.
css folder
CSS Files
static folder
The files that will be delivered statically. They have the folder structure as their route.
Packages included
There are several packages included to help you develop React applications. Here
are some examples of imports
that you can use without configuring anything:
import {/* your imports */} from "react";
import {/* your imports */} from "react/";
import {/* your imports */} from "react-dom";
import {/* your imports */} from "react-dom/server";
import {/* your imports */} from "react-dom/client";
import {/* your imports */} from "react-router-dom";
import {/* your imports */} from "react-router";
import {/* your imports */} from "react/jsx-runtime";
import {/* your imports */} from "render";
import {/* your imports */} from "htm/react";
import {/* your imports */} from "faster";
Creating a project
It is necessary to execute the command:
deno run -A -r "https://deno.land/x/faster_react/new.ts" myProjectFolder
. It
is important to highlight that you need the git command installed and
configured. You can make your customizations and configure the server in
options.json
.
Running a project
It is necessary to execute the command: deno task serve
About
Author: Henrique Emanoel Viana, a Brazilian computer scientist, enthusiast of web technologies, cel: +55 (41) 99999-4664. URL: https://sites.google.com/view/henriqueviana
Improvements and suggestions are welcome!