Fcl JS

Abstract

1. Introduction

This repo is part of the Flow network, a Layer 1 blockchain built for consumer applications, AI Agents, and DeFi at scale.

Connect your dapp to users, their wallets and Flow. Quickstart · Report Bug · Contribute

The Flow Client Library (FCL) JS is a package designed to facilitate interactions between dapps, wallets, and the Flow network. It provides a standardized way for applications to connect with users and their wallets, eliminating the need for custom integrations.

2. Objective

FCL (Flow Client Library) in TypeScript and JavaScript. Connect Flow dApps to wallets, send transactions, and read on-chain data from the browser

This project demonstrates how TypeScript, Web3, JavaScript can be applied to a real-world Blockchain & Cloud Computing problem.

3. Key Features / Modules

• Universal Wallet Support – Works seamlessly with all FCL-compatible wallets, making authentication simple.
• Secure Authentication – Standardized authentication flow ensures a smooth user experience.
• Blockchain Interactions – Enables querying, mutating, and interacting with smart contracts on Flow.
• Full-Featured Utilities – Offers built-in functions to streamline blockchain development.
• Flexible Environment – Can run in both browser and server environments, though wallet interactions are browser-only.

4. Technology Stack

5. System Requirements

General requirements for this technology stack — check the README for exact versions.

• Node.js (LTS) and npm / yarn / pnpm
• VS Code or any code editor
• Node.js (LTS) and npm
• A modern web browser
• Git (to clone the repository)

6. Installation & Setup

git clone https://github.com/onflow/fcl-js.git
cd fcl-js

npm i -S @onflow/fcl

yarn add @onflow/fcl

Full setup instructions are in the project README.

7. Future Enhancements

Suggested extensions you can add to make this your own project.

• Add a CI/CD pipeline with GitHub Actions
• Deploy to a public test network or cloud free tier
• Add monitoring and cost alerts

8. Viva / Review Questions

Common questions examiners ask for projects in this domain.

1. Why does this problem need a blockchain or cloud-native design?
2. Explain the smart contract / infrastructure components and how they interact.
3. How are gas costs or cloud costs kept under control?
4. How is the system secured (keys, IAM, access control)?
5. How would the solution scale to many more users?

9. Source Code & License

This project is developed by onflow and published on GitHub under the Apache License 2.0. Please follow the license terms and credit the original author when you use or modify this code.