package
React at the edge.
npm install bladeGitHub-flavored package documentation.
Across all versions.
Download trend unavailable.
Runtime metadata.
Tagged topics.
A React framework for building instant web apps.
pages/index.tsx and package.json are needed to get Blade to run)Blade purposefully does not (and likely won't ever) comply with the official specification for React Server Components, because it provides different solutions to the problems that RSC aims to solve.
To get started with Blade, create a new app with this command:
npm create bladeAfterward, enter the newly created directory and install the dependencies:
cd blade-example
npm installLastly, start the development server:
npm run devIn order to deploy your Blade app to production, use your deployment provider of choice. For example, you can sign up to Vercel and run this command in the directory of your Blade app to deploy it:
vercel -yThat's all. The command will create the Vercel project and deploy the app for you.
Check out the documentation for more details.
To start contributing code, clone the repo and install its dependencies:
bun installOnce that's done, link the package to make it available to all of your local projects, by running the following command in the packages/blade directory:
bun linkInside your project, you can then run the following command, which is similar to bun add blade or npm install blade, except that it doesn't install blade from npm, but instead uses your local clone of the package:
bun link bladeIf your project is not yet compatible with Bun, feel free to replace all of the occurrences of the word bun in the commands above with npm instead.
You will just need to make sure that, once you create a pull request on the current repo, it will not contain a package-lock.json file, which is usually generated by npm. Instead, we're using the bun.lockb file for this purpose (locking sub dependencies to a certain version).
Before you create a pull request on the blade repo, it is advised to run its tests in order to ensure everything works as expected:
# Run all tests
bun run test
# Alternatively, run a single test
bun run test -- -t 'your test name'leo
mindrun@icloud.com
/api for you, for models that you want to expose)Estimated unpacked size across 33 packages.
35.4 MB
Includes dependencies.
10 direct · 5 outdated
2.1.13
2.1.13
16.5.0
18.0.10
1.0.0-beta.53
1.3.2
5.0.0
5.0.0
3.0.0
3.0.0
0.101.0
4.1.16
4.3.5
3.0.0