《Fullstack React》：ReactJS与朋友的全面指南

3星 · 超过75%的资源需积分: 10 79 浏览量更新于2024-07-19 收藏 19.53MB PDF 举报

"《Fullstack React：The Complete Book on ReactJS and Friends》是一本由安东尼·阿科马佐、阿里·伦纳、内特·默里、克莱·奥尔索普、大卫·古特曼和泰勒·麦金尼斯合著的全面指南，涵盖了React.js及相关技术。本书专为那些希望深入理解React及其生态系统的人设计，特别适合全栈开发者。作者们在编写过程中，技术顾问是索菲亚·肖梅克，确保了内容的专业性和准确性。本书由Fullstack.io出版，于2017年5月18日发布。版权所有，禁止任何形式的复制或传播，除非出于购买者的个人备份或存档目的。代码可以在项目中自由使用，无论商业还是其他用途。尽管作者和出版商已尽全力准备，但对书中信息或程序的错误或遗漏概不承担明确或隐含的保证，也不对因使用书中的信息或程序导致的偶然或间接损害负责。本书采用Leanpub排版，出版地在加利福尼亚州旧金山。本书包括以下章节： 1. 书稿修订历史 - 记录了版本更新的重要信息。 2. 报告bug - 提供途径让读者向作者反馈发现的问题。 3. 与社区互动 - 鼓励读者通过Twitter了解最新动态并参与讨论。 4. 获取更新通知 - 告知读者如何保持对更新内容的了解。 5. 致读者 - 开篇的欢迎词，可能包含对读者的期待和指导。 6. 引言 - 作者或出版社对React及其重要性的介绍。 7. 如何开始 - 包括安装、设置和基础知识的学习路径。 8. React核心概念 - 深入解析React组件、虚拟DOM等关键原理。 9. React生态 - 探讨Redux、React Router、Webpack等周边技术。 10. 实战项目 - 提供实际开发案例，帮助读者应用所学知识。 11. 工程最佳实践 - 讨论代码组织、测试和性能优化策略。 12. 进阶主题 - 针对高级开发者探讨React Fiber、Context API等高级特性。 13. 未来趋势 - 分析React的发展方向及新兴技术。《Fullstack React：The Complete Book on ReactJS and Friends》是一本全面且实用的React技术参考书，旨在帮助读者建立扎实的React基础，并掌握整个前端开发栈。通过阅读这本书，读者将不仅能深入了解React，还能跟上行业发展趋势，提升自己的技能水平。"

CONTENTS

The spread operator (...) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822

Enhanced object literals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823

Default arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823

Destructuring assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824

Changelog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827

Revision 31 - 2017-05-18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827

Revision 30 - 2017-04-20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827

Revision 29 - 2017-04-13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827

Revision 28 - 2017-04-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827

Revision 27 - 2017-03-16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827

Revision 26 - 2017-02-22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827

Revision 25 - 2017-02-17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828

Revision 24 - 2017-02-08 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828

Revision 23 - 2017-02-06 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828

Revision 22 - 2017-02-01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828

Revision 21 - 2017-01-27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828

Revision 20 - 2017-01-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828

Revision 19 - 2016-12-20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828

Revision 18 - 2016-11-22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829

Revision 17 - 2016-11-04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829

Revision 16 - 2016-10-12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829

Revision 15 - 2016-10-05 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829

Revision 14 - 2016-08-26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829

Revision 13 - 2016-08-02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829

Revision 12 - 2016-07-26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829

Revision 11 - 2016-07-08 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829

Revision 10 - 2016-06-24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829

Revision 9 - 2016-06-21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830

Revision 8 - 2016-06-02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830

Revision 7 - 2016-05-13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830

Revision 6 - 2016-05-13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830

Revision 5 - 2016-04-25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830

Revision 4 - 2016-04-22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830

Revision 3 - 2016-04-08 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830

Revision 2 - 2016-03-16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830

Revision 1 - 2016-02-14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831

Foreword

Web development is often seen as a crazy world where the way you develop software is by throwing

hacks on top of hacks. I believe that React breaks from this pattern and instead has been designed

from first principle which gives you a solid foundation to build on.

Christopher Chedeau - Front-end Engineer

at Facebook

A major source of bugs for front-end applications was

around synchronizing the data model with the DOM. It

is very hard to make sure that whenever data changes,

everything in the UI is updated with it.

React’s first innovation was to introduce a pure-

JavaScript representation of the DOM and implement

diffing in userland and then use events which send

simple commands: create, update, delete.

With React, by conceptually re-rendering everything

whenever anything changes, not only do you have

code that is safe by default, it is also less work as you

only need to write the creation path: updates are taken

care of for you.

Browsers have, for a long time, been incompatible in

various ways due to the large API surface area of what

they have to support to make the DOM work. Not only

does React provide a great way to solve browser differences, but it enables use cases that were never

before possible for a front-end library, such as server-side rendering and the ability to implement

rendering targets like native iOS, Android, and even hardware components.

But the most important thing about React and the main reason why you should read this book: not

only will you use it to make great applications for your users, it will also make you a better

developer. Libraries come and go all the time and React is likely going to be no exception. What

makes it special is that it teaches you concepts that can be reused throughout your entire career.

You will become better at JavaScript because React doesn’t come with a templating system.

Instead, React pushes you to use the full power of JavaScript to build your user interface.

You are going to practice using parts of functional programming with map and filter and also

encouraged to use the latest features of JavaScript (including ES6). By not abstracting away data

management, React will force you to think about how to architect your app and encourage you to

consider concepts like immutability.

I’m very proud that the community built around React is not afraid of “rethinking best practices.”

The community challenges the status quo in many areas. My advice to you is to read this excellent

How to Get the Most Out of This Book

Overview

This book aims to be the single most useful resource on learning React. By the time you’re done

reading this book, you (and your team) will have everything you need to build reliable, powerful

React apps.

React core is lean and powerful. After the first few chapters, you’ll have a solid understanding of

React’s fundamentals and will be able to build a wide array of rich, interactive web apps with the

framework.

But beyond React’s core, there are many tools in its ecosystem that you might find helpful for

building production apps. Things like client-side routing between pages, managing complex state,

and heavy API interaction at scale.

This book consists of two parts.

In Part I, we cover all the fundamentals with a progressive, example-driven approach. You’ll create

your first apps, learn how to write components, start handling user interaction, manage rich

forms, and even interact with servers.

We bookend the first part by exploring the inner workings of Create React App (Facebook’s tool

for running React apps), writing automated unit tests, and building a multi-page app that uses

client-side routing.

Part II of this book moves into more advanced concepts that you’ll see used in large, production

applications. These concepts explore strategies for data architecture, transport, and management:

Redux is a state management paradigm based on Facebook’s Flux architecture. Redux provides a

structure for large state trees and allows you to decouple user interaction in your app from state

changes.

GraphQL is a powerful, typed, REST API alternative where the client describes the data it needs.

We also cover how to write your own GraphQL servers for your own data.

Relay is the glue between GraphQL and React. Relay is a data-fetching library that makes it easy to

write flexible, performant apps without a lot of data-fetching code.

Finally, in the last chapter, we’ll talk about how to write native, cross-platform mobile apps using

React Native.

There are a few guidelines we want to give you in order to get the most out of this book.

First, know that you do not need to read this book linearly from cover-to-cover. However, we’ve

ordered the contents of the book in a way we feel fits the order you should learn the concepts. We

剩余849页未读，继续阅读

iOSDevLog

粉丝: 17
资源: 21

《Fullstack React》：ReactJS与朋友的全面指南

Fullstack.React.The Complete Book on ReactJS and Friends.r20.2017.1.pdf

qrcode.react库

全部的react API

PC端react pdf预览组件

qrcode.react 二维码logo

pdf.js react

React Hook "useTranslation" is called in function "getSymptomList" that is neither a React function component nor a custom React Hook function. React component names must start with an uppercase letter. React Hook names must start with the word "use".

react.reactproptypes

spring react

最新资源