2022-05-19
1911
#css#react#web3
MacBobby Chibuzor
111936
May 19, 2022 ⋅ 6 min read

Full-stack DApp tutorial with Vite + React, Tailwind CSS, and Solidity

MacBobby Chibuzor Go, Solidity, and Haskell developer interested in the cloud native world and blockchain technology. A fanatic for technical writing and open source contribution.

Recent posts:

Using Llama Index To Add Personal Data To Large Language Models

Using LlamaIndex to add personal data to LLMs

LlamaIndex provides tools for ingesting, processing, and implementing complex query workflows that combine data access with LLM prompting.

Ukeje Goodness
Jul 23, 2024 ⋅ 5 min read
JavaScript logo on top of violet background

Exploring essential DOM methods for frontend development

Learn four groups of DOM methods and their uses to create responsive and dynamic webpages. A helpful DOM reference table is also included.

Chimezie Innocent
Jul 23, 2024 ⋅ 12 min read
Playwright Adoption Guide: Overview, Examples, And Alternatives

Playwright adoption guide: Overview, examples, and alternatives

Playwright has become one of the leading technologies for writing end-to-end tests for modern web apps thanks to its rich and intuitive API.

Antonello Zanini
Jul 22, 2024 ⋅ 15 min read
Exploring The Javascript Registry For Javascript Module Management

Exploring JSR for JavaScript module management

JSR is designed to serve as a registry for both JavaScript and TypeScript packages, and an upgrade to the features provided by npm.

Oyinkansola Awosan
Jul 19, 2024 ⋅ 8 min read
View all posts

2 Replies to "Full-stack DApp tutorial with Vite + React, Tailwind CSS, and Solidity"

  1. Have you seen moralis.io ? Speeds up web3 dev like crazy😅
    : Please check it out, it makes Dapps dev smoother and faster

    So we’ll just be needing => {

    React
    Solidity
    Moralis
    Remix
    }

    Nice content, I love the way you simplified your solidity though.
    This is my first time here👌

  2. Incomplete article. Footer.jsx, Loader.jsx, Navigation_bar.sx not being used anywhere. Neither is the transactionContext. Nor is the ABI.
    There is no interaction between the frontend and the smart contract.
    It looks like the article got truncated. Please fix it.

Leave a Reply