process1212

狼叔来找翻译人员了--plato--持续翻译中.....

这个项目是使用 Create React App引导的。

你将在下面找到如何执行常见任务的一些信息。

你可以在这找到最新版本的指南。

更新到新版本
发送反馈
文件夹结构
可用的脚本
- npm start
- npm test
- npm run build
- npm run eject
支持的浏览器
支持的语言功能
编辑器中语法高亮
编辑器中显示Lint输出
编辑器中进行调试
自动化格式代码
改变页面 </code></li> <li>安装依赖项</li> <li>导入组件</li> <li>代码拆分</li> <li>添加样式表</li> <li>添加CSS模块样式表</li> <li>添加Sass样式表</li> <li>后处理CSS</li> <li>添加图像，字体和文件</li> <li>添加SVG</li> <li>使用 <code>public</code> 文件夹 <ul> <li>更改HTML</li> <li>在模块系统外添加资源</li> <li>何时使用 <code>public</code> 文件夹</li> </ul> </li> <li>使用全局变量</li> <li>添加 Bootstrap <ul> <li>使用自定义主题</li> </ul> </li> <li>添加流</li> <li>添加中继</li> <li>添加路由器</li> <li>添加自定义环境变量 <ul> <li>在HTML中引用环境变量</li> <li>在Shell中添加临时环境变量</li> <li>添加开发环境变量 <code>.env</code></li> </ul> </li> <li>我可以使用装饰器吗?</li> <li>使用AJAX请求获取数据</li> <li>与后端API集成 <ul> <li>Node</li> <li>Ruby on Rails</li> </ul> </li> <li>在开发中代理API请求 <ul> <li>配置代理后出现“无效主机标头”错误</li> <li>手动配置代理</li> </ul> </li> <li>在开发中使用HTTPS</li> <li>在服务器上生成动态标签 <code><meta></code> </li> <li>预渲染HTML静态文件</li> <li>将数据从服务器注入页面</li> <li>运行测试 <ul> <li>文件名约定</li> <li>命令行界面</li> <li>版本控制集成</li> <li>写测试</li> <li>测试组件</li> <li>使用第三方断言库</li> <li>初始化测试环境</li> <li>聚焦和排除第三方环境</li> <li>覆盖率报告</li> <li>持续集成</li> <li>禁用jsdom</li> <li>快照测试</li> <li>编辑器集成</li> </ul> </li> <li>调试测试 <ul> <li>在Chrome中调试测试</li> <li>在Visual Studio Code中调试测试</li> </ul> </li> <li>隔离开发组件 <ul> <li>由Storybook开始</li> <li>由Styleguidist开始</li> </ul> </li> <li>发布组件到npm</li> <li>做渐进式Web应用程序 <ul> <li>为什么选择加入？</li> <li>离线优考虑因素</li> <li>渐进式Web应用程序元数据</li> </ul> </li> <li>分析Bundle大小</li> <li>部署 <ul> <li>静态服务器</li> <li>其他方案</li> <li>使用客户端路由提供应用支持</li> <li>相对路径构建</li> <li>为任意构建环境定制环境变量</li> <li>Azure</li> <li>Firebase</li> <li>GitHub Pages</li> <li>Heroku</li> <li>Netlify</li> <li>Now</li> <li>S3 and CloudFront</li> <li>Surge</li> </ul> </li> <li>高级配置</li> <li>故障排除 <ul> <li><code>npm start</code> 没有检测到变化</li> <li><code>npm test</code> 在macOS Sierra上挂起或崩溃</li> <li><code>npm run build</code> 过早退出</li> <li><code>npm run build</code> Heroku失败</li> <li><code>npm run build</code> 压缩失败</li> <li>缺少Moment.js环境</li> </ul> </li> <li>Ejecting替代品</li> <li>有什么遗漏?</li> </ul> <h3>更新到新版本</h3> Create React App分为两个包: <ul> <li><code>create-react-app</code> 是一个全局命令行实用程序，可用于创建新项目。</li> <li><code>react-scripts</code> 是生成的项目中的开发依赖项（包括此项）。</li> </ul> 你几乎从不需要更新<code>create-react-app</code> : 它将所有设置委托给 <code>react-scripts</code>. 当你运行 <code>create-react-app</code>时, 它总是实用 <code>react-scripts</code>的最新版本创建项目，因此你将自动获得新创建的应用程序中所有功能和改进。. 更新现有项目到一个新版本的 <code>react-scripts</code>，打开更改日志，找到你当前所在的版本 (如果你不确定可以在在文件中检查 <code>package.json</code> )，并应用新版本的迁移说明。 在大多数情况下自底向上模块化程序设计在<code>package.json</code> 的 <code>react-scripts</code> 版本并运行 <code>npm install</code> (或者 <code>yarn install</code>) 在这个文件夹中已经足够了,但最好查看更改日志以了解可能发生的重大变化。 我们承诺将破坏性保持在最低限度，一遍您可以轻松升级<code>react-scripts</code> 。 <h3>发送反馈</h3> 我们随时欢迎您的反馈. <h3>文件夹结构</h3> 创建后，您的项目应如下所示: <pre><code>my-app/ README.md node_modules/ package.json public/ index.html favicon.ico src/ App.css App.js App.test.js index.css index.js logo.svg </code></pre> 对于要构建的目录, 这些文件必须与确切的文件名一起存在: <ul> <li><code>public/index.html</code> 这是页面模版;</li> <li><code>src/index.js</code> 是JavaScript的入口点。</li> </ul> 您可以删除或重命名其他文件。 您可以在 <code>src</code>里面创建子目录。为了加快重建的速度, 只有在 <code>src</code>里的文件被WebPack处理。 你需要把任何JS和CSS文件放在<code>src</code>里面，否则WebPack不会看到他们。 只有在<code>public</code>里的文件能够从<code>public/index.html</code>被使用。 阅读以下有关使用JavaScript和HTML资源的说明 但是，您可以创建更多顶级目录。 它们不会包含在生产版本中，因此您可以将它们用于文档等内容。 如果您安装了Git并且您的项目不是更大的存储库的一部分，那么将初始化一个新的存储库，从而产生一个额外的 <code>.git/</code>顶级目录。 <h3>可用的脚本</h3> 在项目目录中，您可以运行： <h4><code>npm start</code></h4> 在开发模式下运行应用程序。 打开http://localhost:3000在浏览器中查看它。 如果您进行编辑，页面将重新加载。 您还将在控制台中看到任何lint错误。 <h4><code>npm test</code></h4> 以交互式监视模式启动测试运行器。 有关更多信息，请参阅有关运行测试的部分。 <h4><code>npm run build</code></h4> 构建用于生产的应用程序到<code>build</code>文件夹。 它正确地将React捆绑在生产模式中并优化构建以获得最佳性能。 构建被压缩，文件名包含哈希。 您的应用已准备好部署！ 有关更多信息，请参阅有关部署的部分。 <h4><code>npm run eject</code></h4> 注意：这是一个单项操作，一旦 <code>eject</code>，你就不能回去！ 如果您对构建工具和配置选择不满意，您可以随时<code>eject</code>。此命令将从项目中删除单个构建依赖项。 相反，它会将所有配置文件和传递依赖项（Webpack，Babel，ESLint等）复制到项目中，以便您可以完全控制它们。所有的命令除了<code>eject</code>之外将仍然有效，但它们将指向复制的脚本，以便您可以调整它们。在这一点上，你是独立的。 你不必使用<code>eject</code>。精选功能集适用于中小型部署，您不应觉得有义务使用此功能。但是，我们知道如果您准备好它时无法自定义此工具将无用。 <h3>支持的浏览器</h3> 默认情况下，生成的项目支持所有现代浏览器。 对Internet Explorer 9,10和11的支持需要polyfills. <h4>支持的语言功能</h4> 该项目支持最新JavaScript标准的超集。 除了ES6语法功能外，它还支持： <ul> <li>Exponentiation Operator (ES2016).</li> <li>Async/await (ES2017).</li> <li>Object Rest/Spread Properties (ES2018).</li> <li>Dynamic import() (stage 3 proposal)</li> <li>Class Fields and Static Properties (part of stage 3 proposal).</li> <li>JSX and Flow syntax.</li> </ul> Learn more about different proposal stages. While we recommend using experimental proposals with some caution, Facebook heavily uses these features in the product code, so we intend to provide codemods if any of these proposals change in the future. Note that this project includes no polyfills by default. If you use any other ES6+ features that need runtime support (such as <code>Array.from()</code> or <code>Symbol</code>), make sure you are including the appropriate polyfills manually, or that the browsers you are targeting already support them. <h3>Syntax Highlighting in the Editor</h3> To configure the syntax highlighting in your favorite text editor, head to the relevant Babel documentation page and follow the instructions. Some of the most popular editors are covered. <h3>Displaying Lint Output in the Editor</h3> <blockquote> Note: this feature is available with <code>react-scripts@0.2.0</code> and higher. It also only works with npm 3 or higher. </blockquote> Some editors, including Sublime Text, Atom, and Visual Studio Code, provide plugins for ESLint. They are not required for linting. You should see the linter output right in your terminal as well as the browser console. However, if you prefer the lint results to appear right in your editor, there are some extra steps you can do. You would need to install an ESLint plugin for your editor first. Then, add a file called <code>.eslintrc</code> to the project root: <pre><code class="prism language-js">{ "extends": "react-app" } </code></pre> Now your editor should report the linting warnings. Note that even if you edit your <code>.eslintrc</code> file further, these changes will only affect the editor integration. They won’t affect the terminal and in-browser lint output. This is because Create React App intentionally provides a minimal set of rules that find common mistakes. If you want to enforce a coding style for your project, consider using Prettier instead of ESLint style rules. <h3>Debugging in the Editor</h3> This feature is currently only supported by Visual Studio Code and WebStorm. Visual Studio Code and WebStorm support debugging out of the box with Create React App. This enables you as a developer to write and debug your React code without leaving the editor, and most importantly it enables you to have a continuous development workflow, where context switching is minimal, as you don’t have to switch between tools. <h4>Visual Studio Code</h4> You would need to have the latest version of VS Code and VS Code Chrome Debugger Extension installed. Then add the block below to your <code>launch.json</code> file and put it inside the <code>.vscode</code> folder in your app’s root directory. <pre><code class="prism language-json">{ "version": "0.2.0", "configurations": [ { "name": "Chrome", "type": "chrome", "request": "launch", "url": "http://localhost:3000", "webRoot": "${workspaceRoot}/src", "sourceMapPathOverrides": { "webpack:///src/*": "${webRoot}/*" } } ] } </code></pre> <blockquote> Note: the URL may be different if you’ve made adjustments via the HOST or PORT environment variables. </blockquote> Start your app by running <code>npm start</code>, and start debugging in VS Code by pressing <code>F5</code> or by clicking the green debug icon. You can now write code, set breakpoints, make changes to the code, and debug your newly modified code—all from your editor. Having problems with VS Code Debugging? Please see their troubleshooting guide. <h4>WebStorm</h4> You would need to have WebStorm and JetBrains IDE Support Chrome extension installed. In the WebStorm menu <code>Run</code> select <code>Edit Configurations...</code>. Then click <code>+</code> and select <code>JavaScript Debug</code>. Paste <code>http://localhost:3000</code> into the URL field and save the configuration. <blockquote> Note: the URL may be different if you’ve made adjustments via the HOST or PORT environment variables. </blockquote> Start your app by running <code>npm start</code>, then press <code>^D</code> on macOS or <code>F9</code> on Windows and Linux or click the green debug icon to start debugging in WebStorm. The same way you can debug your application in IntelliJ IDEA Ultimate, PhpStorm, PyCharm Pro, and RubyMine. <h3>Formatting Code Automatically</h3> Prettier is an opinionated code formatter with support for JavaScript, CSS and JSON. With Prettier you can format the code you write automatically to ensure a code style within your project. See the Prettier’s GitHub page for more information, and look at this page to see it in action. To format our code whenever we make a commit in git, we need to install the following dependencies: <pre><code class="prism language-sh">npm install --save husky lint-staged prettier </code></pre> Alternatively you may use <code>yarn</code>: <pre><code class="prism language-sh">yarn add husky lint-staged prettier </code></pre> <ul> <li><code>husky</code> makes it easy to use githooks as if they are npm scripts.</li> <li><code>lint-staged</code> allows us to run scripts on staged files in git. See this blog post about lint-staged to learn more about it.</li> <li><code>prettier</code> is the JavaScript formatter we will run before commits.</li> </ul> Now we can make sure every file is formatted correctly by adding a few lines to the <code>package.json</code> in the project root. Add the following field to the <code>package.json</code> section: <pre><code class="prism language-diff">+ "husky": { + "hooks": { + "pre-commit": "lint-staged" + } + } </code></pre> Next we add a ‘lint-staged’ field to the <code>package.json</code>, for example: <pre><code class="prism language-diff"> "dependencies": { // ... }, + "lint-staged": { + "src/**/*.{js,jsx,json,css}": [ + "prettier --single-quote --write", + "git add" + ] + }, "scripts": { </code></pre> Now, whenever you make a commit, Prettier will format the changed files automatically. You can also run <code>./node_modules/.bin/prettier --single-quote --write "src/**/*.{js,jsx}"</code> to format your entire project for the first time. Next you might want to integrate Prettier in your favorite editor. Read the section on Editor Integration on the Prettier GitHub page. <h3>Changing the Page <code><title></code></h3> You can find the source HTML file in the <code>public</code> folder of the generated project. You may edit the <code><title></code> tag in it to change the title from “React App” to anything else. Note that normally you wouldn’t edit files in the <code>public</code> folder very often. For example, adding a stylesheet is done without touching the HTML. If you need to dynamically update the page title based on the content, you can use the browser <code>document.title</code> API. For more complex scenarios when you want to change the title from React components, you can use React Helmet, a third party library. If you use a custom server for your app in production and want to modify the title before it gets sent to the browser, you can follow advice in this section. Alternatively, you can pre-build each page as a static HTML file which then loads the JavaScript bundle, which is covered here. <h3>Installing a Dependency</h3> The generated project includes React and ReactDOM as dependencies. It also includes a set of scripts used by Create React App as a development dependency. You may install other dependencies (for example, React Router) with <code>npm</code>: <pre><code class="prism language-sh">npm install --save react-router-dom </code></pre> Alternatively you may use <code>yarn</code>: <pre><code class="prism language-sh">yarn add react-router-dom </code></pre> This works for any library, not just <code>react-router-dom</code>. <h3>Importing a Component</h3> This project setup supports ES6 modules thanks to Webpack. While you can still use <code>require()</code> and <code>module.exports</code>, we encourage you to use <code>import</code> and <code>export</code> instead. For example: <h4><code>Button.js</code></h4> <pre><code class="prism language-js">import React, { Component } from 'react'; class Button extends Component { render() { // ... } } export default Button; // Don’t forget to use export default! </code></pre> <h4><code>DangerButton.js</code></h4> <pre><code class="prism language-js">import React, { Component } from 'react'; import Button from './Button'; // Import a component from another file class DangerButton extends Component { render() { return <Button color="red" />; } } export default DangerButton; </code></pre> Be aware of the difference between default and named exports. It is a common source of mistakes. We suggest that you stick to using default imports and exports when a module only exports a single thing (for example, a component). That’s what you get when you use <code>export default Button</code> and <code>import Button from './Button'</code>. Named exports are useful for utility modules that export several functions. A module may have at most one default export and as many named exports as you like. Learn more about ES6 modules: <ul> <li>When to use the curly braces?</li> <li>Exploring ES6: Modules</li> <li>Understanding ES6: Modules</li> </ul> <h3>Code Splitting</h3> Instead of downloading the entire app before users can use it, code splitting allows you to split your code into small chunks which you can then load on demand. This project setup supports code splitting via dynamic <code>import()</code>. Its proposal is in stage 3. The <code>import()</code> function-like form takes the module name as an argument and returns a <code>Promise</code> which always resolves to the namespace object of the module. Here is an example: <h4><code>moduleA.js</code></h4> <pre><code class="prism language-js">const moduleA = 'Hello'; export { moduleA }; </code></pre> <h4><code>App.js</code></h4> <pre><code class="prism language-js">import React, { Component } from 'react'; class App extends Component { handleClick = () => { import('./moduleA') .then(({ moduleA }) => { // Use moduleA }) .catch(err => { // Handle failure }); }; render() { return ( <div> <button onClick={this.handleClick}>Load</button> </div> ); } } export default App; </code></pre> This will make <code>moduleA.js</code> and all its unique dependencies as a separate chunk that only loads after the user clicks the ‘Load’ button. You can also use it with <code>async</code> / <code>await</code> syntax if you prefer it. <h4>With React Router</h4> If you are using React Router check out this tutorial on how to use code splitting with it. You can find the companion GitHub repository here. Also check out the Code Splitting section in React documentation. <h3>Adding a Stylesheet</h3> This project setup uses Webpack for handling all assets. Webpack offers a custom way of “extending” the concept of <code>import</code> beyond JavaScript. To express that a JavaScript file depends on a CSS file, you need to import the CSS from the JavaScript file: <h4><code>Button.css</code></h4> <pre><code class="prism language-css">.Button { padding: 20px; } </code></pre> <h4><code>Button.js</code></h4> <pre><code class="prism language-js">import React, { Component } from 'react'; import './Button.css'; // Tell Webpack that Button.js uses these styles class Button extends Component { render() { // You can use them as regular CSS styles return <div className="Button" />; } } </code></pre> This is not required for React but many people find this feature convenient. You can read about the benefits of this approach here. However you should be aware that this makes your code less portable to other build tools and environments than Webpack. In development, expressing dependencies this way allows your styles to be reloaded on the fly as you edit them. In production, all CSS files will be concatenated into a single minified <code>.css</code> file in the build output. If you are concerned about using Webpack-specific semantics, you can put all your CSS right into <code>src/index.css</code>. It would still be imported from <code>src/index.js</code>, but you could always remove that import if you later migrate to a different build tool. <h3>Adding a CSS Modules Stylesheet</h3> <blockquote> Note: this feature is available with <code>react-scripts@2.0.0</code> and higher. </blockquote> This project supports CSS Modules alongside regular stylesheets using the <code>[name].module.css</code> file naming convention. CSS Modules allows the scoping of CSS by automatically creating a unique classname of the format <code>[filename]\_[classname]\_\_[hash]</code>. <blockquote> Tip: Should you want to preprocess a stylesheet with Sass then make sure to follow the installation instructions and then change the stylesheet file extension as follows: <code>[name].module.scss</code> or <code>[name].module.sass</code>. </blockquote> CSS Modules let you use the same CSS class name in different files without worrying about naming clashes. Learn more about CSS Modules here. <h4><code>Button.module.css</code></h4> <pre><code class="prism language-css">.error { background-color: red; } </code></pre> <h4><code>another-stylesheet.css</code></h4> <pre><code class="prism language-css">.error { color: red; } </code></pre> <h4><code>Button.js</code></h4> <pre><code class="prism language-js">import React, { Component } from 'react'; import styles from './Button.module.css'; // Import css modules stylesheet as styles import './another-stylesheet.css'; // Import regular stylesheet class Button extends Component { render() { // reference as a js object return <button className={styles.error}>Error Button</button>; } } </code></pre> <h4>Result</h4> No clashes from other <code>.error</code> class names <pre><code class="prism language-html"> <button class="Button_error_ax7yz"></div> </code></pre> This is an optional feature. Regular <code><link></code> stylesheets and CSS files are fully supported. CSS Modules are turned on for files ending with the <code>.module.css</code> extension. <h3>Adding a Sass Stylesheet</h3> <blockquote> Note: this feature is available with <code>react-scripts@2.0.0</code> and higher. </blockquote> Generally, we recommend that you don’t reuse the same CSS classes across different components. For example, instead of using a <code>.Button</code> CSS class in <code><AcceptButton></code> and <code><RejectButton></code> components, we recommend creating a <code><Button></code> component with its own <code>.Button</code> styles, that both <code><AcceptButton></code> and <code><RejectButton></code> can render (but not inherit). Following this rule often makes CSS preprocessors less useful, as features like mixins and nesting are replaced by component composition. You can, however, integrate a CSS preprocessor if you find it valuable. To use Sass, first install <code>node-sass</code>: <pre><code class="prism language-bash">$ npm install node-sass --save $ # or $ yarn add node-sass </code></pre> Now you can rename <code>src/App.css</code> to <code>src/App.scss</code> and update <code>src/App.js</code> to import <code>src/App.scss</code>. This file and any other file will be automatically compiled if imported with the extension <code>.scss</code> or <code>.sass</code>. To share variables between Sass files, you can use Sass imports. For example, <code>src/App.scss</code> and other component style files could include <code>@import "./shared.scss";</code> with variable definitions. This will allow you to do imports like <pre><code class="prism language-scss">@import 'styles/_colors.scss'; // assuming a styles directory under src/ @import '~nprogress/nprogress'; // importing a css file from the nprogress node module </code></pre> <blockquote> Tip: You can opt into using this feature with CSS modules too! </blockquote> <blockquote> Note: You must prefix imports from <code>node_modules</code> with <code>~</code> as displayed above. </blockquote> <blockquote> Note: If you’re using Flow, add the following to your <code>.flowconfig</code> so it’ll recognize the <code>.sass</code> or <code>.scss</code> imports. </blockquote> <pre><code>[options] module.file_ext=.sass module.file_ext=.scss </code></pre> <h3>Post-Processing CSS</h3> This project setup minifies your CSS and adds vendor prefixes to it automatically through Autoprefixer so you don’t need to worry about it. Support for new CSS features like the <code>all</code> property, <code>break</code> properties, custom properties, and media query ranges are automatically polyfilled to add support for older browsers. You can customize your target support browsers by adjusting the <code>browserslist</code> key in <code>package.json</code> according to the Browserslist specification. For example, this: <pre><code class="prism language-css">.App { display: flex; flex-direction: row; align-items: center; } </code></pre> becomes this: <pre><code class="prism language-css">.App { display: -webkit-box; display: -ms-flexbox; display: flex; -webkit-box-orient: horizontal; -webkit-box-direction: normal; -ms-flex-direction: row; flex-direction: row; -webkit-box-align: center; -ms-flex-align: center; align-items: center; } </code></pre> If you need to disable autoprefixing for some reason, follow this section. CSS Grid Layout prefixing is disabled by default, but it will not strip manual prefixing. If you’d like to opt-in to CSS Grid prefixing, first familiarize yourself about its limitations. To enable CSS Grid prefixing, add <code>/* autoprefixer grid: on */</code> to the top of your CSS file. <h3>Adding Images, Fonts, and Files</h3> With Webpack, using static assets like images and fonts works similarly to CSS. You can <code>import</code> a file right in a JavaScript module. This tells Webpack to include that file in the bundle. Unlike CSS imports, importing a file gives you a string value. This value is the final path you can reference in your code, e.g. as the <code>src</code> attribute of an image or the <code>href</code> of a link to a PDF. To reduce the number of requests to the server, importing images that are less than 10,000 bytes returns a data URI instead of a path. This applies to the following file extensions: bmp, gif, jpg, jpeg, and png. SVG files are excluded due to #1153. Here is an example: <pre><code class="prism language-js">import React from 'react'; import logo from './logo.png'; // Tell Webpack this JS file uses this image console.log(logo); // /logo.84287d09.png function Header() { // Import result is the URL of your image return <img src={logo} alt="Logo" />; } export default Header; </code></pre> This ensures that when the project is built, Webpack will correctly move the images into the build folder, and provide us with correct paths. This works in CSS too: <pre><code class="prism language-css">.Logo { background-image: url(./logo.png); } </code></pre> Webpack finds all relative module references in CSS (they start with <code>./</code>) and replaces them with the final paths from the compiled bundle. If you make a typo or accidentally delete an important file, you will see a compilation error, just like when you import a non-existent JavaScript module. The final filenames in the compiled bundle are generated by Webpack from content hashes. If the file content changes in the future, Webpack will give it a different name in production so you don’t need to worry about long-term caching of assets. Please be advised that this is also a custom feature of Webpack. It is not required for React but many people enjoy it (and React Native uses a similar mechanism for images). An alternative way of handling static assets is described in the next section. <h4>Adding SVGs</h4> <blockquote> Note: this feature is available with <code>react-scripts@2.0.0</code> and higher. </blockquote> One way to add SVG files was described in the section above. You can also import SVGs directly as React components. You can use either of the two approaches. In your code it would look like this: <pre><code class="prism language-js">import { ReactComponent as Logo } from './logo.svg'; const App = () => ( <div> {/* Logo is an actual React component */} <Logo /> </div> ); </code></pre> This is handy if you don’t want to load SVG as a separate file. Don’t forget the curly braces in the import! The <code>ReactComponent</code> import name is special and tells Create React App that you want a React component that renders an SVG, rather than its filename. <h3>Using the <code>public</code> Folder</h3> <blockquote> Note: this feature is available with <code>react-scripts@0.5.0</code> and higher. </blockquote> <h4>Changing the HTML</h4> The <code>public</code> folder contains the HTML file so you can tweak it, for example, to set the page title. The <code><script></code> tag with the compiled code will be added to it automatically during the build process. <h4>Adding Assets Outside of the Module System</h4> You can also add other assets to the <code>public</code> folder. Note that we normally encourage you to <code>import</code> assets in JavaScript files instead. For example, see the sections on adding a stylesheet and adding images and fonts. This mechanism provides a number of benefits: <ul> <li>Scripts and stylesheets get minified and bundled together to avoid extra network requests.</li> <li>Missing files cause compilation errors instead of 404 errors for your users.</li> <li>Result filenames include content hashes so you don’t need to worry about browsers caching their old versions.</li> </ul> However there is an escape hatch that you can use to add an asset outside of the module system. If you put a file into the <code>public</code> folder, it will not be processed by Webpack. Instead it will be copied into the build folder untouched. To reference assets in the <code>public</code> folder, you need to use a special variable called <code>PUBLIC_URL</code>. Inside <code>index.html</code>, you can use it like this: <pre><code class="prism language-html"><link rel="shortcut icon" href="%PUBLIC_URL%/favicon.ico"> </code></pre> Only files inside the <code>public</code> folder will be accessible by <code>%PUBLIC_URL%</code> prefix. If you need to use a file from <code>src</code> or <code>node_modules</code>, you’ll have to copy it there to explicitly specify your intention to make this file a part of the build. When you run <code>npm run build</code>, Create React App will substitute <code>%PUBLIC_URL%</code> with a correct absolute path so your project works even if you use client-side routing or host it at a non-root URL. In JavaScript code, you can use <code>process.env.PUBLIC_URL</code> for similar purposes: <pre><code class="prism language-js">render() { // Note: this is an escape hatch and should be used sparingly! // Normally we recommend using `import` for getting asset URLs // as described in “Adding Images and Fonts” above this section. return <img src={process.env.PUBLIC_URL + '/img/logo.png'} />; } </code></pre> Keep in mind the downsides of this approach: <ul> <li>None of the files in <code>public</code> folder get post-processed or minified.</li> <li>Missing files will not be called at compilation time, and will cause 404 errors for your users.</li> <li>Result filenames won’t include content hashes so you’ll need to add query arguments or rename them every time they change.</li> </ul> <h4>When to Use the <code>public</code> Folder</h4> Normally we recommend importing stylesheets, images, and fonts from JavaScript. The <code>public</code> folder is useful as a workaround for a number of less common cases: <ul> <li>You need a file with a specific name in the build output, such as <code>manifest.webmanifest</code>.</li> <li>You have thousands of images and need to dynamically reference their paths.</li> <li>You want to include a small script like <code>pace.js</code> outside of the bundled code.</li> <li>Some library may be incompatible with Webpack and you have no other option but to include it as a <code><script></code> tag.</li> </ul> Note that if you add a <code><script></code> that declares global variables, you also need to read the next section on using them. <h3>Using Global Variables</h3> When you include a script in the HTML file that defines global variables and try to use one of these variables in the code, the linter will complain because it cannot see the definition of the variable. You can avoid this by reading the global variable explicitly from the <code>window</code> object, for example: <pre><code class="prism language-js">const $ = window.$; </code></pre> This makes it obvious you are using a global variable intentionally rather than because of a typo. Alternatively, you can force the linter to ignore any line by adding <code>// eslint-disable-line</code> after it. <h3>Adding Bootstrap</h3> You don’t have to use reactstrap together with React but it is a popular library for integrating Bootstrap with React apps. If you need it, you can integrate it with Create React App by following these steps: Install reactstrap and Bootstrap from npm. reactstrap does not include Bootstrap CSS so this needs to be installed as well: <pre><code class="prism language-sh">npm install --save reactstrap bootstrap@4 </code></pre> Alternatively you may use <code>yarn</code>: <pre><code class="prism language-sh">yarn add bootstrap@4 reactstrap </code></pre> Import Bootstrap CSS and optionally Bootstrap theme CSS in the beginning of your <code>src/index.js</code> file: <pre><code class="prism language-js">import 'bootstrap/dist/css/bootstrap.css'; // Put any other imports below so that CSS from your // components takes precedence over default styles. </code></pre> Import required reactstrap components within <code>src/App.js</code> file or your custom component files: <pre><code class="prism language-js">import { Button } from 'reactstrap'; </code></pre> Now you are ready to use the imported reactstrap components within your component hierarchy defined in the render method. Here is an example <code>App.js</code> redone using reactstrap. <h4>Using a Custom Theme</h4> <blockquote> Note: this feature is available with <code>react-scripts@2.0.0</code> and higher. </blockquote> Sometimes you might need to tweak the visual styles of Bootstrap (or equivalent package). As of <code>react-scripts@2.0.0</code> you can import <code>.scss</code> files. This makes it possible to use a package’s built-in Sass variables for global style preferences. To customize Bootstrap, create a file called <code>src/custom.scss</code> (or similar) and import the Bootstrap source stylesheet. Add any overrides before the imported file(s). You can reference Bootstrap’s documentation for the names of the available variables. <pre><code class="prism language-scss">// Override default variables before the import $body-bg: #000; // Import Bootstrap and its default variables @import '~bootstrap/scss/bootstrap.scss'; </code></pre> <blockquote> Note: You must prefix imports from <code>node_modules</code> with <code>~</code> as displayed above. </blockquote> Finally, import the newly created <code>.scss</code> file instead of the default Bootstrap <code>.css</code> in the beginning of your <code>src/index.js</code> file, for example: <pre><code class="prism language-javascript">import './custom.scss'; </code></pre> <h3>Adding Flow</h3> Flow is a static type checker that helps you write code with fewer bugs. Check out this introduction to using static types in JavaScript if you are new to this concept. Recent versions of Flow work with Create React App projects out of the box. To add Flow to a Create React App project, follow these steps: <ol> <li>Run <code>npm install --save flow-bin</code> (or <code>yarn add flow-bin</code>).</li> <li>Add <code>"flow": "flow"</code> to the <code>scripts</code> section of your <code>package.json</code>.</li> <li>Run <code>npm run flow init</code> (or <code>yarn flow init</code>) to create a <code>.flowconfig</code> file in the root directory.</li> <li>Add <code>// @flow</code> to any files you want to type check (for example, to <code>src/App.js</code>).</li> </ol> Now you can run <code>npm run flow</code> (or <code>yarn flow</code>) to check the files for type errors. You can optionally use an IDE like Nuclide for a better integrated experience. In the future we plan to integrate it into Create React App even more closely. To learn more about Flow, check out its documentation. <h3>Adding Relay</h3> Relay is a framework for building data-driven React applications powered by GraphQL. The current release candidate of Relay works with Create React App projects out of the box using Babel Macros. Simply set up your project as laid out in the Relay documentation, then make sure you have a version of the babel plugin providing the macro. To add it, run: <pre><code class="prism language-sh">npm install --save --dev babel-plugin-relay@dev </code></pre> Alternatively you may use <code>yarn</code>: <pre><code class="prism language-sh">yarn upgrade babel-plugin-relay@dev </code></pre> Then, wherever you use the <code>graphql</code> template tag, import the macro: <pre><code class="prism language-js">import graphql from 'babel-plugin-relay/macro'; // instead of: // import { graphql } from "babel-plugin-relay" graphql` query UserQuery { viewer { id } } `; </code></pre> To learn more about Relay, check out its documentation. <h3>Adding a Router</h3> Create React App doesn’t prescribe a specific routing solution, but React Router is the most popular one. To add it, run: <pre><code class="prism language-sh">npm install --save react-router-dom </code></pre> Alternatively you may use <code>yarn</code>: <pre><code class="prism language-sh">yarn add react-router-dom </code></pre> To try it, delete all the code in <code>src/App.js</code> and replace it with any of the examples on its website. The Basic Example is a good place to get started. Note that you may need to configure your production server to support client-side routing before deploying your app. <h3>Adding Custom Environment Variables</h3> <blockquote> Note: this feature is available with <code>react-scripts@0.2.3</code> and higher. </blockquote> Your project can consume variables declared in your environment as if they were declared locally in your JS files. By default you will have <code>NODE_ENV</code> defined for you, and any other environment variables starting with <code>REACT_APP_</code>. The environment variables are embedded during the build time. Since Create React App produces a static HTML/CSS/JS bundle, it can’t possibly read them at runtime. To read them at runtime, you would need to load HTML into memory on the server and replace placeholders in runtime, just like described here. Alternatively you can rebuild the app on the server anytime you change them. <blockquote> Note: You must create custom environment variables beginning with <code>REACT_APP_</code>. Any other variables except <code>NODE_ENV</code> will be ignored to avoid accidentally exposing a private key on the machine that could have the same name. Changing any environment variables will require you to restart the development server if it is running. </blockquote> These environment variables will be defined for you on <code>process.env</code>. For example, having an environment variable named <code>REACT_APP_SECRET_CODE</code> will be exposed in your JS as <code>process.env.REACT_APP_SECRET_CODE</code>. There is also a special built-in environment variable called <code>NODE_ENV</code>. You can read it from <code>process.env.NODE_ENV</code>. When you run <code>npm start</code>, it is always equal to <code>'development'</code>, when you run <code>npm test</code> it is always equal to <code>'test'</code>, and when you run <code>npm run build</code> to make a production bundle, it is always equal to <code>'production'</code>. You cannot override <code>NODE_ENV</code> manually. This prevents developers from accidentally deploying a slow development build to production. These environment variables can be useful for displaying information conditionally based on where the project is deployed or consuming sensitive data that lives outside of version control. First, you need to have environment variables defined. For example, let’s say you wanted to consume a secret defined in the environment inside a <code><form></code>: <pre><code class="prism language-jsx">render() { return ( <div> You are running this application in {process.env.NODE_ENV} mode. <form> <input type="hidden" defaultValue={process.env.REACT_APP_SECRET_CODE} /> </form> </div> ); } </code></pre> During the build, <code>process.env.REACT_APP_SECRET_CODE</code> will be replaced with the current value of the <code>REACT_APP_SECRET_CODE</code> environment variable. Remember that the <code>NODE_ENV</code> variable will be set for you automatically. When you load the app in the browser and inspect the <code><input></code>, you will see its value set to <code>abcdef</code>, and the bold text will show the environment provided when using <code>npm start</code>: <pre><code class="prism language-html"><div> <small>You are running this application in <b>development</b> mode.</small> <form> <input type="hidden" value="abcdef" /> </form> </div> </code></pre> The above form is looking for a variable called <code>REACT_APP_SECRET_CODE</code> from the environment. In order to consume this value, we need to have it defined in the environment. This can be done using two ways: either in your shell or in a <code>.env</code> file. Both of these ways are described in the next few sections. Having access to the <code>NODE_ENV</code> is also useful for performing actions conditionally: <pre><code class="prism language-js">if (process.env.NODE_ENV !== 'production') { analytics.disable(); } </code></pre> When you compile the app with <code>npm run build</code>, the minification step will strip out this condition, and the resulting bundle will be smaller. <h4>Referencing Environment Variables in the HTML</h4> <blockquote> Note: this feature is available with <code>react-scripts@0.9.0</code> and higher. </blockquote> You can also access the environment variables starting with <code>REACT_APP_</code> in the <code>public/index.html</code>. For example: <pre><code class="prism language-html"><title>%REACT_APP_WEBSITE_NAME%</title> </code></pre> Note that the caveats from the above section apply: <ul> <li>Apart from a few built-in variables (<code>NODE_ENV</code> and <code>PUBLIC_URL</code>), variable names must start with <code>REACT_APP_</code> to work.</li> <li>The environment variables are injected at build time. If you need to inject them at runtime, follow this approach instead.</li> </ul> <h4>Adding Temporary Environment Variables In Your Shell</h4> Defining environment variables can vary between OSes. It’s also important to know that this manner is temporary for the life of the shell session. <h5>Windows (cmd.exe)</h5> <pre><code class="prism language-cmd">set "REACT_APP_SECRET_CODE=abcdef" && npm start </code></pre> (Note: Quotes around the variable assignment are required to avoid a trailing whitespace.) <h5>Windows (Powershell)</h5> <pre><code class="prism language-Powershell">($env:REACT_APP_SECRET_CODE = "abcdef") -and (npm start) </code></pre> <h5>Linux, macOS (Bash)</h5> <pre><code class="prism language-bash">REACT_APP_SECRET_CODE=abcdef npm start </code></pre> <h4>Adding Development Environment Variables In <code>.env</code></h4> <blockquote> Note: this feature is available with <code>react-scripts@0.5.0</code> and higher. </blockquote> To define permanent environment variables, create a file called <code>.env</code> in the root of your project: <pre><code>REACT_APP_SECRET_CODE=abcdef </code></pre> <blockquote> Note: You must create custom environment variables beginning with <code>REACT_APP_</code>. Any other variables except <code>NODE_ENV</code> will be ignored to avoid accidentally exposing a private key on the machine that could have the same name. Changing any environment variables will require you to restart the development server if it is running. </blockquote> <code>.env</code> files should be checked into source control (with the exclusion of <code>.env*.local</code>). <h5>What other <code>.env</code> files can be used?</h5> <blockquote> Note: this feature is available with <code>react-scripts@1.0.0</code> and higher. </blockquote> <ul> <li><code>.env</code>: Default.</li> <li><code>.env.local</code>: Local overrides. This file is loaded for all environments except test.</li> <li><code>.env.development</code>, <code>.env.test</code>, <code>.env.production</code>: Environment-specific settings.</li> <li><code>.env.development.local</code>, <code>.env.test.local</code>, <code>.env.production.local</code>: Local overrides of environment-specific settings.</li> </ul> Files on the left have more priority than files on the right: <ul> <li><code>npm start</code>: <code>.env.development.local</code>, <code>.env.development</code>, <code>.env.local</code>, <code>.env</code></li> <li><code>npm run build</code>: <code>.env.production.local</code>, <code>.env.production</code>, <code>.env.local</code>, <code>.env</code></li> <li><code>npm test</code>: <code>.env.test.local</code>, <code>.env.test</code>, <code>.env</code> (note <code>.env.local</code> is missing)</li> </ul> These variables will act as the defaults if the machine does not explicitly set them. Please refer to the dotenv documentation for more details. <blockquote> Note: If you are defining environment variables for development, your CI and/or hosting platform will most likely need these defined as well. Consult their documentation how to do this. For example, see the documentation for Travis CI or Heroku. </blockquote> <h5>Expanding Environment Variables In <code>.env</code></h5> <blockquote> Note: this feature is available with <code>react-scripts@1.1.0</code> and higher. </blockquote> Expand variables already on your machine for use in your <code>.env</code> file (using dotenv-expand). For example, to get the environment variable <code>npm_package_version</code>: <pre><code>REACT_APP_VERSION=$npm_package_version # also works: # REACT_APP_VERSION=${npm_package_version} </code></pre> Or expand variables local to the current <code>.env</code> file: <pre><code>DOMAIN=www.example.com REACT_APP_FOO=$DOMAIN/foo REACT_APP_BAR=$DOMAIN/bar </code></pre> <h3>Can I Use Decorators?</h3> Some popular libraries use decorators in their documentation. Create React App intentionally doesn’t support decorator syntax at the moment because: <ul> <li>It is an experimental proposal and is subject to change (in fact, it has already changed once, and will change again).</li> <li>Most libraries currently support only the old version of the proposal — which will never be a standard.</li> </ul> However in many cases you can rewrite decorator-based code without decorators just as fine. Please refer to these two threads for reference: <ul> <li>#214</li> <li>#411</li> </ul> Create React App will add decorator support when the specification advances to a stable stage. <h3>Fetching Data with AJAX Requests</h3> React doesn’t prescribe a specific approach to data fetching, but people commonly use either a library like axios or the <code>fetch()</code> API provided by the browser. The global <code>fetch</code> function allows you to easily make AJAX requests. It takes in a URL as an input and returns a <code>Promise</code> that resolves to a <code>Response</code> object. You can find more information about <code>fetch</code> here. A Promise represents the eventual result of an asynchronous operation, you can find more information about Promises here and here. Both axios and <code>fetch()</code> use Promises under the hood. You can also use the <code>async / await</code> syntax to reduce the callback nesting. Make sure the <code>fetch()</code> API and Promises are available in your target audience’s browsers. For example, support in Internet Explorer requires a polyfill. You can learn more about making AJAX requests from React components in the FAQ entry on the React website. <h3>Integrating with an API Backend</h3> These tutorials will help you to integrate your app with an API backend running on another port, using <code>fetch()</code> to access it. <h4>Node</h4> Check out this tutorial. You can find the companion GitHub repository here. <h4>Ruby on Rails</h4> Check out this tutorial. You can find the companion GitHub repository here. <h4>API Platform (PHP and Symfony)</h4> API Platform is a framework designed to build API-driven projects. It allows to create hypermedia and GraphQL APIs in minutes. It is shipped with an official Progressive Web App generator as well as a dynamic administration interface, both built for Create React App. Check out this tutorial. <h3>Proxying API Requests in Development</h3> <blockquote> Note: this feature is available with <code>react-scripts@0.2.3</code> and higher. </blockquote> People often serve the front-end React app from the same host and port as their backend implementation. For example, a production setup might look like this after the app is deployed: <pre><code>/ - static server returns index.html with React app /todos - static server returns index.html with React app /api/todos - server handles any /api/* requests using the backend implementation </code></pre> Such setup is not required. However, if you do have a setup like this, it is convenient to write requests like <code>fetch('/api/todos')</code> without worrying about redirecting them to another host or port during development. To tell the development server to proxy any unknown requests to your API server in development, add a <code>proxy</code> field to your <code>package.json</code>, for example: <pre><code class="prism language-js"> "proxy": "http://localhost:4000", </code></pre> This way, when you <code>fetch('/api/todos')</code> in development, the development server will recognize that it’s not a static asset, and will proxy your request to <code>http://localhost:4000/api/todos</code> as a fallback. The development server will only attempt to send requests without <code>text/html</code> in its <code>Accept</code> header to the proxy. Conveniently, this avoids CORS issues and error messages like this in development: <pre><code>Fetch API cannot load http://localhost:4000/api/todos. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3000' is therefore not allowed access. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. </code></pre> Keep in mind that <code>proxy</code> only has effect in development (with <code>npm start</code>), and it is up to you to ensure that URLs like <code>/api/todos</code> point to the right thing in production. You don’t have to use the <code>/api</code> prefix. Any unrecognized request without a <code>text/html</code> accept header will be redirected to the specified <code>proxy</code>. The <code>proxy</code> option supports HTTP, HTTPS and WebSocket connections. If the <code>proxy</code> option is not flexible enough for you, alternatively you can: <ul> <li>Configure the proxy yourself</li> <li>Enable CORS on your server (here’s how to do it for Express).</li> <li>Use environment variables to inject the right server host and port into your app.</li> </ul> <h4>“Invalid Host Header” Errors After Configuring Proxy</h4> When you enable the <code>proxy</code> option, you opt into a more strict set of host checks. This is necessary because leaving the backend open to remote hosts makes your computer vulnerable to DNS rebinding attacks. The issue is explained in this article and this issue. This shouldn’t affect you when developing on <code>localhost</code>, but if you develop remotely like described here, you will see this error in the browser after enabling the <code>proxy</code> option: <blockquote> Invalid Host header </blockquote> To work around it, you can specify your public development host in a file called <code>.env.development</code> in the root of your project: <pre><code>HOST=mypublicdevhost.com </code></pre> If you restart the development server now and load the app from the specified host, it should work. If you are still having issues or if you’re using a more exotic environment like a cloud editor, you can bypass the host check completely by adding a line to <code>.env.development.local</code>. Note that this is dangerous and exposes your machine to remote code execution from malicious websites: <pre><code># NOTE: THIS IS DANGEROUS! # It exposes your machine to attacks from the websites you visit. DANGEROUSLY_DISABLE_HOST_CHECK=true </code></pre> We don’t recommend this approach. <h4>Configuring the Proxy Manually</h4> <blockquote> Note: this feature is available with <code>react-scripts@2.0.0</code> and higher. </blockquote> If the <code>proxy</code> option is not flexible enough for you, you can get direct access to the Express app instance and hook up your own proxy middleware. You can use this feature in conjunction with the <code>proxy</code> property in <code>package.json</code>, but it is recommended you consolidate all of your logic into <code>src/setupProxy.js</code>. First, install <code>http-proxy-middleware</code> using npm or Yarn: <pre><code class="prism language-bash">$ npm install http-proxy-middleware --save $ # or $ yarn add http-proxy-middleware </code></pre> Next, create <code>src/setupProxy.js</code> and place the following contents in it: <pre><code class="prism language-js">const proxy = require('http-proxy-middleware'); module.exports = function(app) { // ... }; </code></pre> You can now register proxies as you wish! Here’s an example using the above <code>http-proxy-middleware</code>: <pre><code class="prism language-js">const proxy = require('http-proxy-middleware'); module.exports = function(app) { app.use(proxy('/api', { target: 'http://localhost:5000/' })); }; </code></pre> <blockquote> Note: You do not need to import this file anywhere. It is automatically registered when you start the development server. </blockquote> <blockquote> Note: This file only supports Node’s JavaScript syntax. Be sure to only use supported language features (i.e. no support for Flow, ES Modules, etc). </blockquote> <blockquote> Note: Passing the path to the proxy function allows you to use globbing and/or pattern matching on the path, which is more flexible than the express route matching. </blockquote> <h3>Using HTTPS in Development</h3> <blockquote> Note: this feature is available with <code>react-scripts@0.4.0</code> and higher. </blockquote> You may require the dev server to serve pages over HTTPS. One particular case where this could be useful is when using the “proxy” feature to proxy requests to an API server when that API server is itself serving HTTPS. To do this, set the <code>HTTPS</code> environment variable to <code>true</code>, then start the dev server as usual with <code>npm start</code>: <h5>Windows (cmd.exe)</h5> <pre><code class="prism language-cmd">set HTTPS=true&&npm start </code></pre> (Note: the lack of whitespace is intentional.) <h5>Windows (Powershell)</h5> <pre><code class="prism language-Powershell">($env:HTTPS = "true") -and (npm start) </code></pre> <h5>Linux, macOS (Bash)</h5> <pre><code class="prism language-bash">HTTPS=true npm start </code></pre> Note that the server will use a self-signed certificate, so your web browser will almost definitely display a warning upon accessing the page. <h3>Generating Dynamic <code><meta></code> Tags on the Server</h3> Since Create React App doesn’t support server rendering, you might be wondering how to make <code><meta></code> tags dynamic and reflect the current URL. To solve this, we recommend to add placeholders into the HTML, like this: <pre><code class="prism language-html"><!doctype html> <html lang="en"> <head> <meta property="og:title" content="__OG_TITLE__"> <meta property="og:description" content="__OG_DESCRIPTION__"> </code></pre> Then, on the server, regardless of the backend you use, you can read <code>index.html</code> into memory and replace <code>__OG_TITLE__</code>, <code>__OG_DESCRIPTION__</code>, and any other placeholders with values depending on the current URL. Just make sure to sanitize and escape the interpolated values so that they are safe to embed into HTML! If you use a Node server, you can even share the route matching logic between the client and the server. However duplicating it also works fine in simple cases. <h3>Pre-Rendering into Static HTML Files</h3> If you’re hosting your <code>build</code> with a static hosting provider you can use react-snapshot or react-snap to generate HTML pages for each route, or relative link, in your application. These pages will then seamlessly become active, or “hydrated”, when the JavaScript bundle has loaded. There are also opportunities to use this outside of static hosting, to take the pressure off the server when generating and caching routes. The primary benefit of pre-rendering is that you get the core content of each page with the HTML payload—regardless of whether or not your JavaScript bundle successfully downloads. It also increases the likelihood that each route of your application will be picked up by search engines. You can read more about zero-configuration pre-rendering (also called snapshotting) here. <h3>Injecting Data from the Server into the Page</h3> Similarly to the previous section, you can leave some placeholders in the HTML that inject global variables, for example: <pre><code class="prism language-js"><!doctype html> <html lang="en"> <head> <script> window.SERVER_DATA = __SERVER_DATA__; </script> </code></pre> Then, on the server, you can replace <code>__SERVER_DATA__</code> with a JSON of real data right before sending the response. The client code can then read <code>window.SERVER_DATA</code> to use it. Make sure to sanitize the JSON before sending it to the client as it makes your app vulnerable to XSS attacks. <h3>Running Tests</h3> <blockquote> Note: this feature is available with <code>react-scripts@0.3.0</code> and higher. </blockquote> <blockquote> Read the migration guide to learn how to enable it in older projects! </blockquote> Create React App uses Jest as its test runner. To prepare for this integration, we did a major revamp of Jest so if you heard bad things about it years ago, give it another try. Jest is a Node-based runner. This means that the tests always run in a Node environment and not in a real browser. This lets us enable fast iteration speed and prevent flakiness. While Jest provides browser globals such as <code>window</code> thanks to jsdom, they are only approximations of the real browser behavior. Jest is intended to be used for unit tests of your logic and your components rather than the DOM quirks. We recommend that you use a separate tool for browser end-to-end tests if you need them. They are beyond the scope of Create React App. <h4>Filename Conventions</h4> Jest will look for test files with any of the following popular naming conventions: <ul> <li>Files with <code>.js</code> suffix in <code>__tests__</code> folders.</li> <li>Files with <code>.test.js</code> suffix.</li> <li>Files with <code>.spec.js</code> suffix.</li> </ul> The <code>.test.js</code> / <code>.spec.js</code> files (or the <code>__tests__</code> folders) can be located at any depth under the <code>src</code> top level folder. We recommend to put the test files (or <code>__tests__</code> folders) next to the code they are testing so that relative imports appear shorter. For example, if <code>App.test.js</code> and <code>App.js</code> are in the same folder, the test just needs to <code>import App from './App'</code> instead of a long relative path. Colocation also helps find tests more quickly in larger projects. <h4>Command Line Interface</h4> When you run <code>npm test</code>, Jest will launch in the watch mode. Every time you save a file, it will re-run the tests, just like <code>npm start</code> recompiles the code. The watcher includes an interactive command-line interface with the ability to run all tests, or focus on a search pattern. It is designed this way so that you can keep it open and enjoy fast re-runs. You can learn the commands from the “Watch Usage” note that the watcher prints after every run: <img src="http://img.e-com-net.com/image/info8/cfaead4d466b456c8709969f86eaeebd.gif" alt="Jest watch mode" width="0" height="0"> <h4>Version Control Integration</h4> By default, when you run <code>npm test</code>, Jest will only run the tests related to files changed since the last commit. This is an optimization designed to make your tests run fast regardless of how many tests you have. However it assumes that you don’t often commit the code that doesn’t pass the tests. Jest will always explicitly mention that it only ran tests related to the files changed since the last commit. You can also press <code>a</code> in the watch mode to force Jest to run all tests. Jest will always run all tests on a continuous integration server or if the project is not inside a Git or Mercurial repository. <h4>Writing Tests</h4> To create tests, add <code>it()</code> (or <code>test()</code>) blocks with the name of the test and its code. You may optionally wrap them in <code>describe()</code> blocks for logical grouping but this is neither required nor recommended. Jest provides a built-in <code>expect()</code> global function for making assertions. A basic test could look like this: <pre><code class="prism language-js">import sum from './sum'; it('sums numbers', () => { expect(sum(1, 2)).toEqual(3); expect(sum(2, 2)).toEqual(4); }); </code></pre> All <code>expect()</code> matchers supported by Jest are extensively documented here. You can also use <code>jest.fn()</code> and <code>expect(fn).toBeCalled()</code> to create “spies” or mock functions. <h4>Testing Components</h4> There is a broad spectrum of component testing techniques. They range from a “smoke test” verifying that a component renders without throwing, to shallow rendering and testing some of the output, to full rendering and testing component lifecycle and state changes. Different projects choose different testing tradeoffs based on how often components change, and how much logic they contain. If you haven’t decided on a testing strategy yet, we recommend that you start with creating simple smoke tests for your components: <pre><code class="prism language-js">import React from 'react'; import ReactDOM from 'react-dom'; import App from './App'; it('renders without crashing', () => { const div = document.createElement('div'); ReactDOM.render(<App />, div); }); </code></pre> This test mounts a component and makes sure that it didn’t throw during rendering. Tests like this provide a lot of value with very little effort so they are great as a starting point, and this is the test you will find in <code>src/App.test.js</code>. When you encounter bugs caused by changing components, you will gain a deeper insight into which parts of them are worth testing in your application. This might be a good time to introduce more specific tests asserting specific expected output or behavior. If you’d like to test components in isolation from the child components they render, we recommend using <code>shallow()</code> rendering API from Enzyme. To install it, run: <pre><code class="prism language-sh">npm install --save enzyme enzyme-adapter-react-16 react-test-renderer </code></pre> Alternatively you may use <code>yarn</code>: <pre><code class="prism language-sh">yarn add enzyme enzyme-adapter-react-16 react-test-renderer </code></pre> As of Enzyme 3, you will need to install Enzyme along with an Adapter corresponding to the version of React you are using. (The examples above use the adapter for React 16.) The adapter will also need to be configured in your global setup file: <h5><code>src/setupTests.js</code></h5> <pre><code class="prism language-js">import { configure } from 'enzyme'; import Adapter from 'enzyme-adapter-react-16'; configure({ adapter: new Adapter() }); </code></pre> <blockquote> Note: Keep in mind that if you decide to “eject” before creating <code>src/setupTests.js</code>, the resulting <code>package.json</code> file won’t contain any reference to it. Read here to learn how to add this after ejecting. </blockquote> Now you can write a smoke test with it: <pre><code class="prism language-js">import React from 'react'; import { shallow } from 'enzyme'; import App from './App'; it('renders without crashing', () => { shallow(<App />); }); </code></pre> Unlike the previous smoke test using <code>ReactDOM.render()</code>, this test only renders <code><App></code> and doesn’t go deeper. For example, even if <code><App></code> itself renders a <code><Button></code> that throws, this test will pass. Shallow rendering is great for isolated unit tests, but you may still want to create some full rendering tests to ensure the components integrate correctly. Enzyme supports full rendering with <code>mount()</code>, and you can also use it for testing state changes and component lifecycle. You can read the Enzyme documentation for more testing techniques. Enzyme documentation uses Chai and Sinon for assertions but you don’t have to use them because Jest provides built-in <code>expect()</code> and <code>jest.fn()</code> for spies. Here is an example from Enzyme documentation that asserts specific output, rewritten to use Jest matchers: <pre><code class="prism language-js">import React from 'react'; import { shallow } from 'enzyme'; import App from './App'; it('renders welcome message', () => { const wrapper = shallow(<App />); const welcome = <h2>Welcome to React</h2>; // expect(wrapper.contains(welcome)).toBe(true); expect(wrapper.contains(welcome)).toEqual(true); }); </code></pre> All Jest matchers are extensively documented here. Nevertheless you can use a third-party assertion library like Chai if you want to, as described below. Additionally, you might find jest-enzyme helpful to simplify your tests with readable matchers. The above <code>contains</code> code can be written more simply with jest-enzyme. <pre><code class="prism language-js">expect(wrapper).toContainReact(welcome); </code></pre> To enable this, install <code>jest-enzyme</code>: <pre><code class="prism language-sh">npm install --save jest-enzyme </code></pre> Alternatively you may use <code>yarn</code>: <pre><code class="prism language-sh">yarn add jest-enzyme </code></pre> Import it in <code>src/setupTests.js</code> to make its matchers available in every test: <pre><code class="prism language-js">import 'jest-enzyme'; </code></pre> <h5>Use <code>react-testing-library</code></h5> As an alternative or companion to <code>enzyme</code>, you may consider using <code>react-testing-library</code>. <code>react-testing-library</code> is a library for testing React components in a way that resembles the way the components are used by end users. It is well suited for unit, integration, and end-to-end testing of React components and applications. It works more directly with DOM nodes, and therefore it’s recommended to use with <code>jest-dom</code> for improved assertions. To install <code>react-testing-library</code> and <code>jest-dom</code>, you can run: <pre><code class="prism language-sh">npm install --save react-testing-library jest-dom </code></pre> Alternatively you may use <code>yarn</code>: <pre><code class="prism language-sh">yarn add react-testing-library jest-dom </code></pre> Similar to <code>enzyme</code> you can create a <code>src/setupTests.js</code> file to avoid boilerplate in your test files: <pre><code class="prism language-js">// react-testing-library renders your components to document.body, // this will ensure they're removed after each test. import 'react-testing-library/cleanup-after-each'; // this adds jest-dom's custom assertions import 'jest-dom/extend-expect'; </code></pre> Here’s an example of using <code>react-testing-library</code> and <code>jest-dom</code> for testing that the <code><App /></code> component renders “Welcome to React”. <pre><code class="prism language-js">import React from 'react'; import { render } from 'react-testing-library'; import App from './App'; it('renders welcome message', () => { const { getByText } = render(<App />); expect(getByText('Welcome to React')).toBeInTheDocument(); }); </code></pre> Learn more about the utilities provided by <code>react-testing-library</code> to facilitate testing asynchronous interactions as well as selecting form elements from the <code>react-testing-library</code> documentation and examples. <h4>Using Third Party Assertion Libraries</h4> We recommend that you use <code>expect()</code> for assertions and <code>jest.fn()</code> for spies. If you are having issues with them please file those against Jest, and we’ll fix them. We intend to keep making them better for React, supporting, for example, pretty-printing React elements as JSX. However, if you are used to other libraries, such as Chai and Sinon, or if you have existing code using them that you’d like to port over, you can import them normally like this: <pre><code class="prism language-js">import sinon from 'sinon'; import { expect } from 'chai'; </code></pre> and then use them in your tests like you normally do. <h4>Initializing Test Environment</h4> <blockquote> Note: this feature is available with <code>react-scripts@0.4.0</code> and higher. </blockquote> If your app uses a browser API that you need to mock in your tests or if you just need a global setup before running your tests, add a <code>src/setupTests.js</code> to your project. It will be automatically executed before running your tests. For example: <h5><code>src/setupTests.js</code></h5> <pre><code class="prism language-js">const localStorageMock = { getItem: jest.fn(), setItem: jest.fn(), clear: jest.fn(), }; global.localStorage = localStorageMock; </code></pre> <blockquote> Note: Keep in mind that if you decide to “eject” before creating <code>src/setupTests.js</code>, the resulting <code>package.json</code> file won’t contain any reference to it, so you should manually create the property <code>setupTestFrameworkScriptFile</code> in the configuration for Jest, something like the following: </blockquote> <blockquote> <pre><code class="prism language-js">"jest": { // ... "setupTestFrameworkScriptFile": "<rootDir>/src/setupTests.js" } </code></pre> </blockquote> <h4>Focusing and Excluding Tests</h4> You can replace <code>it()</code> with <code>xit()</code> to temporarily exclude a test from being executed. Similarly, <code>fit()</code> lets you focus on a specific test without running any other tests. <h4>Coverage Reporting</h4> Jest has an integrated coverage reporter that works well with ES6 and requires no configuration. Run <code>npm test -- --coverage</code> (note extra <code>--</code> in the middle) to include a coverage report like this: Note that tests run much slower with coverage so it is recommended to run it separately from your normal workflow. <h5>Configuration</h5> The default Jest coverage configuration can be overridden by adding any of the following supported keys to a Jest config in your package.json. Supported overrides: <ul> <li><code>collectCoverageFrom</code></li> <li><code>coverageReporters</code></li> <li><code>coverageThreshold</code></li> <li><code>snapshotSerializers</code></li> </ul> Example package.json: <pre><code class="prism language-json">{ "name": "your-package", "jest": { "collectCoverageFrom": [ "src/**/*.{js,jsx}", "!<rootDir>/node_modules/", "!<rootDir>/path/to/dir/" ], "coverageThreshold": { "global": { "branches": 90, "functions": 90, "lines": 90, "statements": 90 } }, "coverageReporters": ["text"], "snapshotSerializers": ["my-serializer-module"] } } </code></pre> <h4>Continuous Integration</h4> By default <code>npm test</code> runs the watcher with interactive CLI. However, you can force it to run tests once and finish the process by setting an environment variable called <code>CI</code>. When creating a build of your application with <code>npm run build</code> linter warnings are not checked by default. Like <code>npm test</code>, you can force the build to perform a linter warning check by setting the environment variable <code>CI</code>. If any warnings are encountered then the build fails. Popular CI servers already set the environment variable <code>CI</code> by default but you can do this yourself too: <h4>On CI servers</h4> <h5>Travis CI</h5> <ol> <li>Following the Travis Getting started guide for syncing your GitHub repository with Travis. You may need to initialize some settings manually in your profile page.</li> <li>Add a <code>.travis.yml</code> file to your git repository.</li> </ol> <pre><code>language: node_js node_js: - 8 cache: directories: - node_modules script: - npm run build - npm test </code></pre> <ol> <li>Trigger your first build with a git push.</li> <li>Customize your Travis CI Build if needed.</li> </ol> <h5>CircleCI</h5> Follow this article to set up CircleCI with a Create React App project. <h4>On your own environment</h4> <h6>Windows (cmd.exe)</h6> <pre><code class="prism language-cmd">set CI=true&&npm test </code></pre> <pre><code class="prism language-cmd">set CI=true&&npm run build </code></pre> (Note: the lack of whitespace is intentional.) <h6>Windows (Powershell)</h6> <pre><code class="prism language-Powershell">($env:CI = $true) -and (npm test) </code></pre> <pre><code class="prism language-Powershell">($env:CI = $true) -and (npm run build) </code></pre> <h6>Linux, macOS (Bash)</h6> <pre><code class="prism language-bash">CI=true npm test </code></pre> <pre><code class="prism language-bash">CI=true npm run build </code></pre> The test command will force Jest to run tests once instead of launching the watcher. <blockquote> If you find yourself doing this often in development, please file an issue to tell us about your use case because we want to make watcher the best experience and are open to changing how it works to accommodate more workflows. </blockquote> The build command will check for linter warnings and fail if any are found. <h4>Disabling jsdom</h4> If you know that none of your tests depend on jsdom, you can safely set <code>--env=node</code>, and your tests will run faster: <pre><code class="prism language-diff"> "scripts": { "start": "react-scripts start", "build": "react-scripts build", - "test": "react-scripts test" + "test": "react-scripts test --env=node" </code></pre> To help you make up your mind, here is a list of APIs that need jsdom: <ul> <li>Any browser globals like <code>window</code> and <code>document</code></li> <li><code>ReactDOM.render()</code></li> <li><code>TestUtils.renderIntoDocument()</code> (a shortcut for the above)</li> <li><code>mount()</code> in Enzyme</li> </ul> In contrast, jsdom is not needed for the following APIs: <ul> <li><code>TestUtils.createRenderer()</code> (shallow rendering)</li> <li><code>shallow()</code> in Enzyme</li> </ul> Finally, jsdom is also not needed for snapshot testing. <h4>Snapshot Testing</h4> Snapshot testing is a feature of Jest that automatically generates text snapshots of your components and saves them on the disk so if the UI output changes, you get notified without manually writing any assertions on the component output. Read more about snapshot testing. <h4>Editor Integration</h4> If you use Visual Studio Code, there is a Jest extension which works with Create React App out of the box. This provides a lot of IDE-like features while using a text editor: showing the status of a test run with potential fail messages inline, starting and stopping the watcher automatically, and offering one-click snapshot updates. <img src="http://img.e-com-net.com/image/info8/fd9c9da699584e0faad9124883e4db87.jpg" alt="VS Code Jest Preview" width="0" height="0"> <h3>Debugging Tests</h3> There are various ways to setup a debugger for your Jest tests. We cover debugging in Chrome and Visual Studio Code. <blockquote> Note: debugging tests requires Node 8 or higher. </blockquote> <h4>Debugging Tests in Chrome</h4> Add the following to the <code>scripts</code> section in your project’s <code>package.json</code> <pre><code class="prism language-json">"scripts": { "test:debug": "react-scripts --inspect-brk test --runInBand" } </code></pre> Place <code>debugger;</code> statements in any test and run: <pre><code class="prism language-bash">$ npm run test:debug </code></pre> This will start running your Jest tests, but pause before executing to allow a debugger to attach to the process. Open the following in Chrome <pre><code>about:inspect </code></pre> After opening that link, the Chrome Developer Tools will be displayed. Select <code>inspect</code> on your process and a breakpoint will be set at the first line of the react script (this is done simply to give you time to open the developer tools and to prevent Jest from executing before you have time to do so). Click the button that looks like a “play” button in the upper right hand side of the screen to continue execution. When Jest executes the test that contains the debugger statement, execution will pause and you can examine the current scope and call stack. <blockquote> Note: the --runInBand cli option makes sure Jest runs test in the same process rather than spawning processes for individual tests. Normally Jest parallelizes test runs across processes but it is hard to debug many processes at the same time. </blockquote> <h4>Debugging Tests in Visual Studio Code</h4> Debugging Jest tests is supported out of the box for Visual Studio Code. Use the following <code>launch.json</code> configuration file: <pre><code>{ "version": "0.2.0", "configurations": [ { "name": "Debug CRA Tests", "type": "node", "request": "launch", "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/react-scripts", "args": [ "test", "--runInBand", "--no-cache" ], "cwd": "${workspaceRoot}", "protocol": "inspector", "console": "integratedTerminal", "internalConsoleOptions": "neverOpen" } ] } </code></pre> <h3>Developing Components in Isolation</h3> Usually, in an app, you have a lot of UI components, and each of them has many different states. For an example, a simple button component could have following states: <ul> <li>In a regular state, with a text label.</li> <li>In the disabled mode.</li> <li>In a loading state.</li> </ul> Usually, it’s hard to see these states without running a sample app or some examples. Create React App doesn’t include any tools for this by default, but you can easily add Storybook for React (source) or React Styleguidist (source) to your project. These are third-party tools that let you develop components and see all their states in isolation from your app. You can also deploy your Storybook or style guide as a static app. This way, everyone in your team can view and review different states of UI components without starting a backend server or creating an account in your app. <h4>Getting Started with Storybook</h4> Storybook is a development environment for React UI components. It allows you to browse a component library, view the different states of each component, and interactively develop and test components. First, install the following npm package globally: <pre><code class="prism language-sh">npm install -g @storybook/cli </code></pre> Then, run the following command inside your app’s directory: <pre><code class="prism language-sh">getstorybook </code></pre> After that, follow the instructions on the screen. Learn more about React Storybook: <ul> <li>Learn Storybook (tutorial)</li> <li>Documentation</li> <li>GitHub Repo</li> <li>Snapshot Testing UI with Storybook + addon/storyshot</li> </ul> <h4>Getting Started with Styleguidist</h4> Styleguidist combines a style guide, where all your components are presented on a single page with their props documentation and usage examples, with an environment for developing components in isolation, similar to Storybook. In Styleguidist you write examples in Markdown, where each code snippet is rendered as a live editable playground. First, install Styleguidist: <pre><code class="prism language-sh">npm install --save react-styleguidist </code></pre> Alternatively you may use <code>yarn</code>: <pre><code class="prism language-sh">yarn add react-styleguidist </code></pre> Then, add these scripts to your <code>package.json</code>: <pre><code class="prism language-diff"> "scripts": { + "styleguide": "styleguidist server", + "styleguide:build": "styleguidist build", "start": "react-scripts start", </code></pre> Then, run the following command inside your app’s directory: <pre><code class="prism language-sh">npm run styleguide </code></pre> After that, follow the instructions on the screen. Learn more about React Styleguidist: <ul> <li>GitHub Repo</li> <li>Documentation</li> </ul> <h3>Publishing Components to npm</h3> Create React App doesn’t provide any built-in functionality to publish a component to npm. If you’re ready to extract a component from your project so other people can use it, we recommend moving it to a separate directory outside of your project and then using a tool like nwb to prepare it for publishing. <h3>Making a Progressive Web App</h3> The production build has all the tools necessary to generate a first-class Progressive Web App, but the offline/cache-first behavior is opt-in only. By default, the build process will generate a service worker file, but it will not be registered, so it will not take control of your production web app. In order to opt-in to the offline-first behavior, developers should look for the following in their <code>src/index.js</code> file: <pre><code class="prism language-js">// If you want your app to work offline and load faster, you can change // unregister() to register() below. Note this comes with some pitfalls. // Learn more about service workers: http://bit.ly/CRA-PWA serviceWorker.unregister(); </code></pre> As the comment states, switching <code>serviceWorker.unregister()</code> to <code>serviceWorker.register()</code> will opt you in to using the service worker. <h4>Why Opt-in?</h4> Offline-first Progressive Web Apps are faster and more reliable than traditional web pages, and provide an engaging mobile experience: <ul> <li>All static site assets are cached so that your page loads fast on subsequent visits, regardless of network connectivity (such as 2G or 3G). Updates are downloaded in the background.</li> <li>Your app will work regardless of network state, even if offline. This means your users will be able to use your app at 10,000 feet and on the subway.</li> <li>On mobile devices, your app can be added directly to the user’s home screen, app icon and all. This eliminates the need for the app store.</li> </ul> However, they can make debugging deployments more challenging so, starting with Create React App 2, service workers are opt-in. The <code>workbox-webpack-plugin</code> is integrated into production configuration, and it will take care of generating a service worker file that will automatically precache all of your local assets and keep them up to date as you deploy updates. The service worker will use a cache-first strategy for handling all requests for local assets, including navigation requests for your HTML, ensuring that your web app is consistently fast, even on a slow or unreliable network. <h4>Offline-First Considerations</h4> If you do decide to opt-in to service worker registration, please take the following into account: <ol> <li> After the initial caching is done, the service worker lifecycle controls when updated content ends up being shown to users. In order to guard against race conditions with lazy-loaded content, the default behavior is to conservatively keep the updated service worker in the “waiting” state. This means that users will end up seeing older content until they close (reloading is not enough) their existing, open tabs. See this blog post for more details about this behavior. </li> <li> Users aren’t always familiar with offline-first web apps. It can be useful to let the user know when the service worker has finished populating your caches (showing a “This web app works offline!” message) and also let them know when the service worker has fetched the latest updates that will be available the next time they load the page (showing a “New content is available once existing tabs are closed.” message). Showing this messages is currently left as an exercise to the developer, but as a starting point, you can make use of the logic included in <code>src/serviceWorker.js</code>, which demonstrates which service worker lifecycle events to listen for to detect each scenario, and which as a default, just logs appropriate messages to the JavaScript console. </li> <li> Service workers require HTTPS, although to facilitate local testing, that policy does not apply to <code>localhost</code>. If your production web server does not support HTTPS, then the service worker registration will fail, but the rest of your web app will remain functional. </li> <li> The service worker is only enabled in the production environment, e.g. the output of <code>npm run build</code>. It’s recommended that you do not enable an offline-first service worker in a development environment, as it can lead to frustration when previously cached assets are used and do not include the latest changes you’ve made locally. </li> <li> If you need to test your offline-first service worker locally, build the application (using <code>npm run build</code>) and run a simple http server from your build directory. After running the build script, <code>create-react-app</code> will give instructions for one way to test your production build locally and the deployment instructions have instructions for using other methods. Be sure to always use an incognito window to avoid complications with your browser cache. </li> <li> By default, the generated service worker file will not intercept or cache any cross-origin traffic, like HTTP API requests, images, or embeds loaded from a different domain. </li> </ol> <h4>Progressive Web App Metadata</h4> The default configuration includes a web app manifest located at <code>public/manifest.json</code>, that you can customize with details specific to your web application. When a user adds a web app to their homescreen using Chrome or Firefox on Android, the metadata in <code>manifest.json</code> determines what icons, names, and branding colors to use when the web app is displayed. The Web App Manifest guide provides more context about what each field means, and how your customizations will affect your users’ experience. Progressive web apps that have been added to the homescreen will load faster and work offline when there’s an active service worker. That being said, the metadata from the web app manifest will still be used regardless of whether or not you opt-in to service worker registration. <h3>Analyzing the Bundle Size</h3> Source map explorer analyzes JavaScript bundles using the source maps. This helps you understand where code bloat is coming from. To add Source map explorer to a Create React App project, follow these steps: <pre><code class="prism language-sh">npm install --save source-map-explorer </code></pre> Alternatively you may use <code>yarn</code>: <pre><code class="prism language-sh">yarn add source-map-explorer </code></pre> Then in <code>package.json</code>, add the following line to <code>scripts</code>: <pre><code class="prism language-diff"> "scripts": { + "analyze": "source-map-explorer build/static/js/main.*", "start": "react-scripts start", "build": "react-scripts build", "test": "react-scripts test", </code></pre> Then to analyze the bundle run the production build then run the analyze script. <pre><code>npm run build npm run analyze </code></pre> <h3>Deployment</h3> <code>npm run build</code> creates a <code>build</code> directory with a production build of your app. Set up your favorite HTTP server so that a visitor to your site is served <code>index.html</code>, and requests to static paths like <code>/static/js/main.<hash>.js</code> are served with the contents of the <code>/static/js/main.<hash>.js</code> file. <h4>Static Server</h4> For environments using Node, the easiest way to handle this would be to install serve and let it handle the rest: <pre><code class="prism language-sh">npm install -g serve serve -s build </code></pre> The last command shown above will serve your static site on the port 5000. Like many of serve’s internal settings, the port can be adjusted using the <code>-p</code> or <code>--port</code> flags. Run this command to get a full list of the options available: <pre><code class="prism language-sh">serve -h </code></pre> <h4>Other Solutions</h4> You don’t necessarily need a static server in order to run a Create React App project in production. It works just as fine integrated into an existing dynamic one. Here’s a programmatic example using Node and Express: <pre><code class="prism language-javascript">const express = require('express'); const path = require('path'); const app = express(); app.use(express.static(path.join(__dirname, 'build'))); app.get('/', function(req, res) { res.sendFile(path.join(__dirname, 'build', 'index.html')); }); app.listen(9000); </code></pre> The choice of your server software isn’t important either. Since Create React App is completely platform-agnostic, there’s no need to explicitly use Node. The <code>build</code> folder with static assets is the only output produced by Create React App. However this is not quite enough if you use client-side routing. Read the next section if you want to support URLs like <code>/todos/42</code> in your single-page app. <h4>Serving Apps with Client-Side Routing</h4> If you use routers that use the HTML5 <code>pushState</code> history API under the hood (for example, React Router with <code>browserHistory</code>), many static file servers will fail. For example, if you used React Router with a route for <code>/todos/42</code>, the development server will respond to <code>localhost:3000/todos/42</code> properly, but an Express serving a production build as above will not. This is because when there is a fresh page load for a <code>/todos/42</code>, the server looks for the file <code>build/todos/42</code> and does not find it. The server needs to be configured to respond to a request to <code>/todos/42</code> by serving <code>index.html</code>. For example, we can amend our Express example above to serve <code>index.html</code> for any unknown paths: <pre><code class="prism language-diff"> app.use(express.static(path.join(__dirname, 'build'))); -app.get('/', function (req, res) { +app.get('/*', function (req, res) { res.sendFile(path.join(__dirname, 'build', 'index.html')); }); </code></pre> If you’re using Apache HTTP Server, you need to create a <code>.htaccess</code> file in the <code>public</code> folder that looks like this: <pre><code> Options -MultiViews RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^ index.html [QSA,L] </code></pre> It will get copied to the <code>build</code> folder when you run <code>npm run build</code>. If you’re using Apache Tomcat, you need to follow this Stack Overflow answer. Now requests to <code>/todos/42</code> will be handled correctly both in development and in production. On a production build, and when you’ve opted-in, a service worker will automatically handle all navigation requests, like for <code>/todos/42</code>, by serving the cached copy of your <code>index.html</code>. This service worker navigation routing can be configured or disabled by <code>eject</code>ing and then modifying the <code>navigateFallback</code> and <code>navigateFallbackWhitelist</code> options of the <code>SWPreachePlugin</code> configuration. When users install your app to the homescreen of their device the default configuration will make a shortcut to <code>/index.html</code>. This may not work for client-side routers which expect the app to be served from <code>/</code>. Edit the web app manifest at <code>public/manifest.json</code> and change <code>start_url</code> to match the required URL scheme, for example: <pre><code class="prism language-js"> "start_url": ".", </code></pre> <h4>Building for Relative Paths</h4> By default, Create React App produces a build assuming your app is hosted at the server root. To override this, specify the <code>homepage</code> in your <code>package.json</code>, for example: <pre><code class="prism language-js"> "homepage": "http://mywebsite.com/relativepath", </code></pre> This will let Create React App correctly infer the root path to use in the generated HTML file. Note: If you are using <code>react-router@^4</code>, you can root <code><Link></code>s using the <code>basename</code> prop on any <code><Router></code>. More information here. For example: <pre><code class="prism language-js"><BrowserRouter basename="/calendar"/> <Link to="/today"/> // renders <a href="/calendar/today"> </code></pre> <h5>Serving the Same Build from Different Paths</h5> <blockquote> Note: this feature is available with <code>react-scripts@0.9.0</code> and higher. </blockquote> If you are not using the HTML5 <code>pushState</code> history API or not using client-side routing at all, it is unnecessary to specify the URL from which your app will be served. Instead, you can put this in your <code>package.json</code>: <pre><code class="prism language-js"> "homepage": ".", </code></pre> This will make sure that all the asset paths are relative to <code>index.html</code>. You will then be able to move your app from <code>http://mywebsite.com</code> to <code>http://mywebsite.com/relativepath</code> or even <code>http://mywebsite.com/relative/path</code> without having to rebuild it. <h4>Customizing Environment Variables for Arbitrary Build Environments</h4> You can create an arbitrary build environment by creating a custom <code>.env</code> file and loading it using env-cmd. For example, to create a build environment for a staging environment: <ol> <li>Create a file called <code>.env.staging</code></li> <li>Set environment variables as you would any other <code>.env</code> file (e.g. <code>REACT_APP_API_URL=http://api-staging.example.com</code>)</li> <li>Install env-cmd<pre><code class="prism language-sh">$ npm install env-cmd --save $ # or $ yarn add env-cmd </code></pre> </li> <li>Add a new script to your <code>package.json</code>, building with your new environment:<pre><code class="prism language-json">{ "scripts": { "build:staging": "env-cmd .env.staging npm run build" } } </code></pre> </li> </ol> Now you can run <code>npm run build:staging</code> to build with the staging environment config. You can specify other environments in the same way. Variables in <code>.env.production</code> will be used as fallback because <code>NODE_ENV</code> will always be set to <code>production</code> for a build. <h4>Azure</h4> See this blog post on how to deploy your React app to Microsoft Azure. See this blog post or this repo for a way to use automatic deployment to Azure App Service. <h4>Firebase</h4> Install the Firebase CLI if you haven’t already by running <code>npm install -g firebase-tools</code>. Sign up for a Firebase account and create a new project. Run <code>firebase login</code> and login with your previous created Firebase account. Then run the <code>firebase init</code> command from your project’s root. You need to choose the Hosting: Configure and deploy Firebase Hosting sites and choose the Firebase project you created in the previous step. You will need to agree with <code>database.rules.json</code> being created, choose <code>build</code> as the public directory, and also agree to Configure as a single-page app by replying with <code>y</code>. <pre><code class="prism language-sh"> === Project Setup First, let's associate this project directory with a Firebase project. You can create multiple project aliases by running firebase use --add, but for now we'll just set up a default project. ? What Firebase project do you want to associate as default? Example app (example-app-fd690) === Database Setup Firebase Realtime Database Rules allow you to define how your data should be structured and when your data can be read from and written to. ? What file should be used for Database Rules? database.rules.json ✔ Database Rules for example-app-fd690 have been downloaded to database.rules.json. Future modifications to database.rules.json will update Database Rules when you run firebase deploy. === Hosting Setup Your public directory is the folder (relative to your project directory) that will contain Hosting assets to uploaded with firebase deploy. If you have a build process for your assets, use your build's output directory. ? What do you want to use as your public directory? build ? Configure as a single-page app (rewrite all urls to /index.html)? Yes ✔ Wrote build/index.html i Writing configuration info to firebase.json... i Writing project information to .firebaserc... ✔ Firebase initialization complete! </code></pre> IMPORTANT: you need to set proper HTTP caching headers for <code>service-worker.js</code> file in <code>firebase.json</code> file or you will not be able to see changes after first deployment (issue #2440). It should be added inside <code>"hosting"</code> key like next: <pre><code>{ "hosting": { ... "headers": [ {"source": "/service-worker.js", "headers": [{"key": "Cache-Control", "value": "no-cache"}]} ] ... </code></pre> Now, after you create a production build with <code>npm run build</code>, you can deploy it by running <code>firebase deploy</code>. <pre><code class="prism language-sh"> === Deploying to 'example-app-fd690'... i deploying database, hosting ✔ database: rules ready to deploy. i hosting: preparing build directory for upload... Uploading: [============================== ] 75%✔ hosting: build folder uploaded successfully ✔ hosting: 8 files uploaded successfully i starting release process (may take several minutes)... ✔ Deploy complete! Project Console: https://console.firebase.google.com/project/example-app-fd690/overview Hosting URL: https://example-app-fd690.firebaseapp.com </code></pre> For more information see Add Firebase to your JavaScript Project. <h4>GitHub Pages</h4> <blockquote> Note: this feature is available with <code>react-scripts@0.2.0</code> and higher. </blockquote> <h5>Step 1: Add <code>homepage</code> to <code>package.json</code></h5> The step below is important! If you skip it, your app will not deploy correctly. Open your <code>package.json</code> and add a <code>homepage</code> field for your project: <pre><code class="prism language-json"> "homepage": "https://myusername.github.io/my-app", </code></pre> or for a GitHub user page: <pre><code class="prism language-json"> "homepage": "https://myusername.github.io", </code></pre> or for a custom domain page: <pre><code class="prism language-json"> "homepage": "https://mywebsite.com", </code></pre> Create React App uses the <code>homepage</code> field to determine the root URL in the built HTML file. <h5>Step 2: Install <code>gh-pages</code> and add <code>deploy</code> to <code>scripts</code> in <code>package.json</code></h5> Now, whenever you run <code>npm run build</code>, you will see a cheat sheet with instructions on how to deploy to GitHub Pages. To publish it at https://myusername.github.io/my-app, run: <pre><code class="prism language-sh">npm install --save gh-pages </code></pre> Alternatively you may use <code>yarn</code>: <pre><code class="prism language-sh">yarn add gh-pages </code></pre> Add the following scripts in your <code>package.json</code>: <pre><code class="prism language-diff"> "scripts": { + "predeploy": "npm run build", + "deploy": "gh-pages -d build", "start": "react-scripts start", "build": "react-scripts build", </code></pre> The <code>predeploy</code> script will run automatically before <code>deploy</code> is run. If you are deploying to a GitHub user page instead of a project page you’ll need to make two additional modifications: <ol> <li>First, change your repository’s source branch to be any branch other than master.</li> <li>Additionally, tweak your <code>package.json</code> scripts to push deployments to master:</li> </ol> <pre><code class="prism language-diff"> "scripts": { "predeploy": "npm run build", - "deploy": "gh-pages -d build", + "deploy": "gh-pages -b master -d build", </code></pre> <h5>Step 3: Deploy the site by running <code>npm run deploy</code></h5> Then run: <pre><code class="prism language-sh">npm run deploy </code></pre> <h5>Step 4: Ensure your project’s settings use <code>gh-pages</code></h5> Finally, make sure GitHub Pages option in your GitHub project settings is set to use the <code>gh-pages</code> branch: <h5>Step 5: Optionally, configure the domain</h5> You can configure a custom domain with GitHub Pages by adding a <code>CNAME</code> file to the <code>public/</code> folder. Your CNAME file should look like this: <pre><code>mywebsite.com </code></pre> <h5>Notes on client-side routing</h5> GitHub Pages doesn’t support routers that use the HTML5 <code>pushState</code> history API under the hood (for example, React Router using <code>browserHistory</code>). This is because when there is a fresh page load for a url like <code>http://user.github.io/todomvc/todos/42</code>, where <code>/todos/42</code> is a frontend route, the GitHub Pages server returns 404 because it knows nothing of <code>/todos/42</code>. If you want to add a router to a project hosted on GitHub Pages, here are a couple of solutions: <ul> <li>You could switch from using HTML5 history API to routing with hashes. If you use React Router, you can switch to <code>hashHistory</code> for this effect, but the URL will be longer and more verbose (for example, <code>http://user.github.io/todomvc/#/todos/42?_k=yknaj</code>). Read more about different history implementations in React Router.</li> <li>Alternatively, you can use a trick to teach GitHub Pages to handle 404 by redirecting to your <code>index.html</code> page with a special redirect parameter. You would need to add a <code>404.html</code> file with the redirection code to the <code>build</code> folder before deploying your project, and you’ll need to add code handling the redirect parameter to <code>index.html</code>. You can find a detailed explanation of this technique in this guide.</li> </ul> <h5>Troubleshooting</h5> <h6>“/dev/tty: No such a device or address”</h6> If, when deploying, you get <code>/dev/tty: No such a device or address</code> or a similar error, try the following: <ol> <li>Create a new Personal Access Token</li> <li><code>git remote set-url origin https://<user>:<token>@github.com/<user>/<repo></code> .</li> <li>Try <code>npm run deploy</code> again</li> </ol> <h6>“Cannot read property ‘email’ of null”</h6> If, when deploying, you get <code>Cannot read property 'email' of null</code>, try the following: <ol> <li><code>git config --global user.name '<your_name>'</code></li> <li><code>git config --global user.email '<your_email>'</code></li> <li>Try <code>npm run deploy</code> again</li> </ol> <h4>Heroku</h4> Use the Heroku Buildpack for Create React App. You can find instructions in Deploying React with Zero Configuration. <h5>Resolving Heroku Deployment Errors</h5> Sometimes <code>npm run build</code> works locally but fails during deploy via Heroku. Following are the most common cases. <h6>“Module not found: Error: Cannot resolve ‘file’ or ‘directory’”</h6> If you get something like this: <pre><code>remote: Failed to create a production build. Reason: remote: Module not found: Error: Cannot resolve 'file' or 'directory' MyDirectory in /tmp/build_1234/src </code></pre> It means you need to ensure that the lettercase of the file or directory you <code>import</code> matches the one you see on your filesystem or on GitHub. This is important because Linux (the operating system used by Heroku) is case sensitive. So <code>MyDirectory</code> and <code>mydirectory</code> are two distinct directories and thus, even though the project builds locally, the difference in case breaks the <code>import</code> statements on Heroku remotes. <h6>“Could not find a required file.”</h6> If you exclude or ignore necessary files from the package you will see a error similar this one: <pre><code>remote: Could not find a required file. remote: Name: `index.html` remote: Searched in: /tmp/build_a2875fc163b209225122d68916f1d4df/public remote: remote: npm ERR! Linux 3.13.0-105-generic remote: npm ERR! argv "/tmp/build_a2875fc163b209225122d68916f1d4df/.heroku/node/bin/node" "/tmp/build_a2875fc163b209225122d68916f1d4df/.heroku/node/bin/npm" "run" "build" </code></pre> In this case, ensure that the file is there with the proper lettercase and that’s not ignored on your local <code>.gitignore</code> or <code>~/.gitignore_global</code>. <h4>Netlify</h4> To do a manual deploy to Netlify’s CDN: <pre><code class="prism language-sh">npm install netlify-cli -g netlify deploy </code></pre> Choose <code>build</code> as the path to deploy. To setup continuous delivery: With this setup Netlify will build and deploy when you push to git or open a pull request: <ol> <li>Start a new netlify project</li> <li>Pick your Git hosting service and select your repository</li> <li>Click <code>Build your site</code></li> </ol> Support for client-side routing: To support <code>pushState</code>, make sure to create a <code>public/_redirects</code> file with the following rewrite rules: <pre><code>/* /index.html 200 </code></pre> When you build the project, Create React App will place the <code>public</code> folder contents into the build output. <h4>Now</h4> Now offers a zero-configuration single-command deployment. You can use <code>now</code> to deploy your app for free. <ol> <li> Install the <code>now</code> command-line tool either via the recommended desktop tool or via node with <code>npm install -g now</code>. </li> <li> Build your app by running <code>npm run build</code>. </li> <li> Move into the build directory by running <code>cd build</code>. </li> <li> Run <code>now --name your-project-name</code> from within the build directory. You will see a now.sh URL in your output like this: <pre><code>> Ready! https://your-project-name-tpspyhtdtk.now.sh (copied to clipboard) </code></pre> Paste that URL into your browser when the build is complete, and you will see your deployed app. </li> </ol> Details are available in this article. <h4>S3 and CloudFront</h4> See this blog post on how to deploy your React app to Amazon Web Services S3 and CloudFront. <h4>Surge</h4> Install the Surge CLI if you haven’t already by running <code>npm install -g surge</code>. Run the <code>surge</code> command and log in you or create a new account. When asked about the project path, make sure to specify the <code>build</code> folder, for example: <pre><code class="prism language-sh"> project path: /path/to/project/build </code></pre> Note that in order to support routers that use HTML5 <code>pushState</code> API, you may want to rename the <code>index.html</code> in your build folder to <code>200.html</code> before deploying to Surge. This ensures that every URL falls back to that file. <h3>Advanced Configuration</h3> You can adjust various development and production settings by setting environment variables in your shell or with .env. <table> <thead> <tr> <th align="center">Variable</th> <th align="center">Development</th> <th align="center">Production</th> <th align="left">Usage</th> </tr> </thead> <tbody> <tr> <td align="center">BROWSER</td> <td align="center">✅</td> <td align="center">❌</td> <td align="left">By default, Create React App will open the default system browser, favoring Chrome on macOS. Specify a browser to override this behavior, or set it to <code>none</code> to disable it completely. If you need to customize the way the browser is launched, you can specify a node script instead. Any arguments passed to <code>npm start</code> will also be passed to this script, and the url where your app is served will be the last argument. Your script’s file name must have the <code>.js</code> extension.</td> </tr> <tr> <td align="center">HOST</td> <td align="center">✅</td> <td align="center">❌</td> <td align="left">By default, the development web server binds to <code>localhost</code>. You may use this variable to specify a different host.</td> </tr> <tr> <td align="center">PORT</td> <td align="center">✅</td> <td align="center">❌</td> <td align="left">By default, the development web server will attempt to listen on port 3000 or prompt you to attempt the next available port. You may use this variable to specify a different port.</td> </tr> <tr> <td align="center">HTTPS</td> <td align="center">✅</td> <td align="center">❌</td> <td align="left">When set to <code>true</code>, Create React App will run the development server in <code>https</code> mode.</td> </tr> <tr> <td align="center">PUBLIC_URL</td> <td align="center">❌</td> <td align="center">✅</td> <td align="left">Create React App assumes your application is hosted at the serving web server’s root or a subpath as specified in <code>package.json</code> (<code>homepage</code>). Normally, Create React App ignores the hostname. You may use this variable to force assets to be referenced verbatim to the url you provide (hostname included). This may be particularly useful when using a CDN to host your application.</td> </tr> <tr> <td align="center">CI</td> <td align="center">?</td> <td align="center">✅</td> <td align="left">When set to <code>true</code>, Create React App treats warnings as failures in the build. It also makes the test runner non-watching. Most CIs set this flag by default.</td> </tr> <tr> <td align="center">REACT_EDITOR</td> <td align="center">✅</td> <td align="center">❌</td> <td align="left">When an app crashes in development, you will see an error overlay with clickable stack trace. When you click on it, Create React App will try to determine the editor you are using based on currently running processes, and open the relevant source file. You can send a pull request to detect your editor of choice. Setting this environment variable overrides the automatic detection. If you do it, make sure your systems PATH environment variable points to your editor’s bin folder. You can also set it to <code>none</code> to disable it completely.</td> </tr> <tr> <td align="center">CHOKIDAR_USEPOLLING</td> <td align="center">✅</td> <td align="center">❌</td> <td align="left">When set to <code>true</code>, the watcher runs in polling mode, as necessary inside a VM. Use this option if <code>npm start</code> isn’t detecting changes.</td> </tr> <tr> <td align="center">GENERATE_SOURCEMAP</td> <td align="center">❌</td> <td align="center">✅</td> <td align="left">When set to <code>false</code>, source maps are not generated for a production build. This solves OOM issues on some smaller machines.</td> </tr> <tr> <td align="center">NODE_PATH</td> <td align="center">✅</td> <td align="center">✅</td> <td align="left">Same as <code>NODE_PATH</code> in Node.js, but only relative folders are allowed. Can be handy for emulating a monorepo setup by setting <code>NODE_PATH=src</code>.</td> </tr> <tr> <td align="center">INLINE_RUNTIME_CHUNK</td> <td align="center">❌</td> <td align="center">✅</td> <td align="left">By default, Create React App will embed the runtime script into <code>index.html</code> during the production build. When set to <code>false</code>, the script will not be embedded and will be imported as usual. This is normally required when dealing with CSP.</td> </tr> </tbody> </table> <h3>Troubleshooting</h3> <h4><code>npm start</code> doesn’t detect changes</h4> When you save a file while <code>npm start</code> is running, the browser should refresh with the updated code. If this doesn’t happen, try one of the following workarounds: <ul> <li>If your project is in a Dropbox folder, try moving it out.</li> <li>If the watcher doesn’t see a file called <code>index.js</code> and you’re referencing it by the folder name, you need to restart the watcher due to a Webpack bug.</li> <li>Some editors like Vim and IntelliJ have a “safe write” feature that currently breaks the watcher. You will need to disable it. Follow the instructions in “Adjusting Your Text Editor”.</li> <li>If your project path contains parentheses, try moving the project to a path without them. This is caused by a Webpack watcher bug.</li> <li>On Linux and macOS, you might need to tweak system settings to allow more watchers.</li> <li>If the project runs inside a virtual machine such as (a Vagrant provisioned) VirtualBox, create an <code>.env</code> file in your project directory if it doesn’t exist, and add <code>CHOKIDAR_USEPOLLING=true</code> to it. This ensures that the next time you run <code>npm start</code>, the watcher uses the polling mode, as necessary inside a VM.</li> </ul> If none of these solutions help please leave a comment in this thread. <h4><code>npm test</code> hangs or crashes on macOS Sierra</h4> If you run <code>npm test</code> and the console gets stuck after printing <code>react-scripts test</code> to the console there might be a problem with your Watchman installation as described in facebook/create-react-app#713. We recommend deleting <code>node_modules</code> in your project and running <code>npm install</code> (or <code>yarn</code> if you use it) first. If it doesn’t help, you can try one of the numerous workarounds mentioned in these issues: <ul> <li>facebook/jest#1767</li> <li>facebook/watchman#358</li> <li>ember-cli/ember-cli#6259</li> </ul> It is reported that installing Watchman 4.7.0 or newer fixes the issue. If you use Homebrew, you can run these commands to update it: <pre><code>watchman shutdown-server brew update brew reinstall watchman </code></pre> You can find other installation methods on the Watchman documentation page. If this still doesn’t help, try running <code>launchctl unload -F ~/Library/LaunchAgents/com.github.facebook.watchman.plist</code>. There are also reports that uninstalling Watchman fixes the issue. So if nothing else helps, remove it from your system and try again. <h4><code>npm run build</code> exits too early</h4> It is reported that <code>npm run build</code> can fail on machines with limited memory and no swap space, which is common in cloud environments. Even with small projects this command can increase RAM usage in your system by hundreds of megabytes, so if you have less than 1 GB of available memory your build is likely to fail with the following message: <blockquote> The build failed because the process exited too early. This probably means the system ran out of memory or someone called <code>kill -9</code> on the process. </blockquote> If you are completely sure that you didn’t terminate the process, consider adding some swap space to the machine you’re building on, or build the project locally. <h4><code>npm run build</code> fails on Heroku</h4> This may be a problem with case sensitive filenames. Please refer to this section. <h4>Moment.js locales are missing</h4> If you use a Moment.js, you might notice that only the English locale is available by default. This is because the locale files are large, and you probably only need a subset of all the locales provided by Moment.js. To add a specific Moment.js locale to your bundle, you need to import it explicitly. For example: <pre><code class="prism language-js">import moment from 'moment'; import 'moment/locale/fr'; </code></pre> If you are importing multiple locales this way, you can later switch between them by calling <code>moment.locale()</code> with the locale name: <pre><code class="prism language-js">import moment from 'moment'; import 'moment/locale/fr'; import 'moment/locale/es'; // ... moment.locale('fr'); </code></pre> This will only work for locales that have been explicitly imported before. <h4><code>npm run build</code> fails to minify</h4> Before <code>react-scripts@2.0.0</code>, this problem was caused by third party <code>node_modules</code> using modern JavaScript features because the minifier couldn’t handle them during the build. This has been solved by compiling standard modern JavaScript features inside <code>node_modules</code> in <code>react-scripts@2.0.0</code> and higher. If you’re seeing this error, you’re likely using an old version of <code>react-scripts</code>. You can either fix it by avoiding a dependency that uses modern syntax, or by upgrading to <code>react-scripts@>=2.0.0</code> and following the migration instructions in the changelog. <h3>Alternatives to Ejecting</h3> Ejecting lets you customize anything, but from that point on you have to maintain the configuration and scripts yourself. This can be daunting if you have many similar projects. In such cases instead of ejecting we recommend to fork <code>react-scripts</code> and any other packages you need. This article dives into how to do it in depth. You can find more discussion in this issue. <h3>Something Missing?</h3> If you have ideas for more “How To” recipes that should be on this page, let us know or contribute some! </div> </div> </div> </div> </div>  <div id="SOHUCS" sid="1723060826409086976"></div> <script type="text/javascript" src="/views/front/js/chanyan.js"></script>  <div class="youdao-fixed-ad" id="detail_ad_bottom"></div> </div> <div class="col-md-3"> <div class="row" id="ad">  <div id="right-1" class="col-lg-12 col-md-12 col-sm-4 col-xs-4 ad"> <div class="youdao-fixed-ad" id="detail_ad_1"> </div> </div>  <div id="right-2" class="col-lg-12 col-md-12 col-sm-4 col-xs-4 ad"> <div class="youdao-fixed-ad" id="detail_ad_2"></div> </div>  <div id="right-3" class="col-lg-12 col-md-12 col-sm-4 col-xs-4 ad"> <div class="youdao-fixed-ad" id="detail_ad_3"></div> </div> </div> </div> </div> </div> </div> <div class="container"> <h4 class="pt20 mb15 mt0 border-top">你可能感兴趣的:(transform,plato)</h4> <div id="paradigm-article-related"> <div class="recommend-post mb30"> <ul class="widget-links"> <li><a href="/article/1950227023192453120.htm" title="MotionLCM 部署优化踩坑解决bug" target="_blank">MotionLCM 部署优化踩坑解决bug</a> AI算法网奇 <a class="tag" taget="_blank" href="/search/aigc%E4%B8%8E%E6%95%B0%E5%AD%97%E4%BA%BA/1.htm">aigc与数字人</a><a class="tag" taget="_blank" href="/search/%E6%B7%B1%E5%BA%A6%E5%AD%A6%E4%B9%A0%E5%AE%9D%E5%85%B8/1.htm">深度学习宝典</a><a class="tag" taget="_blank" href="/search/%E6%96%87%E7%94%9Fmotion/1.htm">文生motion</a> <div>目录依赖项windowstorchok：渲染黑白图问题解决：humanml3d：sentence-t5-large下载数据：报错：Nomodulenamed'sentence_transformers'继续报错：fromtransformers.integrationsimportCodeCarbonCallback解决方法：推理相关转mesh：module‘matplotlib.cm‘hasno</div> </li> <li><a href="/article/1950119220717088768.htm" title="基于深度学习的目标检测算法综述：从RCNN到YOLOv13，一文看懂十年演进！" target="_blank">基于深度学习的目标检测算法综述：从RCNN到YOLOv13，一文看懂十年演进！</a> 人工智能教程 <a class="tag" taget="_blank" href="/search/%E6%B7%B1%E5%BA%A6%E5%AD%A6%E4%B9%A0/1.htm">深度学习</a><a class="tag" taget="_blank" href="/search/%E7%9B%AE%E6%A0%87%E6%A3%80%E6%B5%8B/1.htm">目标检测</a><a class="tag" taget="_blank" href="/search/%E7%AE%97%E6%B3%95/1.htm">算法</a><a class="tag" taget="_blank" href="/search/%E4%BA%BA%E5%B7%A5%E6%99%BA%E8%83%BD/1.htm">人工智能</a><a class="tag" taget="_blank" href="/search/%E8%87%AA%E5%8A%A8%E9%A9%BE%E9%A9%B6/1.htm">自动驾驶</a><a class="tag" taget="_blank" href="/search/YOLO/1.htm">YOLO</a><a class="tag" taget="_blank" href="/search/%E6%9C%BA%E5%99%A8%E5%AD%A6%E4%B9%A0/1.htm">机器学习</a> <div>一、引言：目标检测的十年巨变2012年AlexNet拉开深度学习序幕，2014年RCNN横空出世，目标检测从此进入“深度时代”。十年间，算法从两阶段到单阶段，从Anchor-base到Anchor-free，从CNN到Transformer，从2D到3D，从监督学习到自监督学习，迭代速度之快令人目不暇接。本文将系统梳理基于深度学习的目标检测算法，带你全面了解技术演进、核心思想、代表算法、工业落地与</div> </li> <li><a href="/article/1950078258452164608.htm" title="Unity 程序运行一段时间后Game界面出现黑屏的一种情况" target="_blank">Unity 程序运行一段时间后Game界面出现黑屏的一种情况</a> zhannghong2003 <a class="tag" taget="_blank" href="/search/Unity/1.htm">Unity</a><a class="tag" taget="_blank" href="/search/unity/1.htm">unity</a><a class="tag" taget="_blank" href="/search/%E6%B8%B8%E6%88%8F%E5%BC%95%E6%93%8E/1.htm">游戏引擎</a> <div>经过排查，发现是Camera(相机)的Z轴一直变大导致的黑屏。造成这种情况的原因是代码：VMouseTransform.position=Camera.main.ScreenToWorldPoint(Input.mousePosition)；Camera(相机)设置成为跟随VMouseTransform。所以会出现Z轴逐渐变大的情况，最后导致黑屏。改代码为：Vector2vMouseNeed=Ca</div> </li> <li><a href="/article/1950074471545106432.htm" title="C++-coroutines协程将自定义类型转为awaitable(可等待)类型的两种方法" target="_blank">C++-coroutines协程将自定义类型转为awaitable(可等待)类型的两种方法</a> mrbone11 <a class="tag" taget="_blank" href="/search/%23/1.htm">#</a><a class="tag" taget="_blank" href="/search/Coroutines/1.htm">Coroutines</a><a class="tag" taget="_blank" href="/search/c%2B%2B/1.htm">c++</a><a class="tag" taget="_blank" href="/search/%E5%BC%80%E5%8F%91%E8%AF%AD%E8%A8%80/1.htm">开发语言</a><a class="tag" taget="_blank" href="/search/%E5%8D%8F%E7%A8%8B/1.htm">协程</a><a class="tag" taget="_blank" href="/search/coroutines/1.htm">coroutines</a> <div>文章目录前言重载operatorco_await定义promise_type::await_transform函数前言阅读本篇文章时，已经假定你有对协程的基本概念，如果没有，可以阅读我写的这篇协程入门文章我们已经知道，对于co_await\，expression的返回值必须是awaitable类型，即正确实现了如下三个函数：await_readyawait_suspendawait_resume对</div> </li> <li><a href="/article/1950061488773328896.htm" title="视觉Transformer还有哪些点可以研究？怎么应用？" target="_blank">视觉Transformer还有哪些点可以研究？怎么应用？</a> 计算机视觉工坊 <a class="tag" taget="_blank" href="/search/3D%E8%A7%86%E8%A7%89%E4%BB%8E%E5%85%A5%E9%97%A8%E5%88%B0%E7%B2%BE%E9%80%9A/1.htm">3D视觉从入门到精通</a><a class="tag" taget="_blank" href="/search/%E5%AD%A6%E4%B9%A0/1.htm">学习</a><a class="tag" taget="_blank" href="/search/%E7%AE%97%E6%B3%95/1.htm">算法</a><a class="tag" taget="_blank" href="/search/%E5%BC%80%E6%BA%90/1.htm">开源</a> <div>0.这篇文章干了啥？今天笔者为大家推荐一篇最新的综述，详细总结了Transformer的网络架构、优化策略、发展方向，还会定期更新Github，研究注意力机制的小伙伴一定不要错过。注意机制有助于人类视觉系统有效地分析和理解复杂场景，它能够聚焦于图像的关键区域，同时忽略无关紧要的部分。受此概念启发，注意机制已经被引入到计算机视觉（CV）中，以动态地为图像中的不同区域分配权重。这使得神经网络能够专注于</div> </li> <li><a href="/article/1949944219829334016.htm" title="【AI大模型：前沿】43、Mamba架构深度解析：为什么它是Transformer最强挑战者？" target="_blank">【AI大模型：前沿】43、Mamba架构深度解析：为什么它是Transformer最强挑战者？</a> 无心水 <a class="tag" taget="_blank" href="/search/%E6%9E%B6%E6%9E%84/1.htm">架构</a><a class="tag" taget="_blank" href="/search/transformer/1.htm">transformer</a><a class="tag" taget="_blank" href="/search/Mamba/1.htm">Mamba</a><a class="tag" taget="_blank" href="/search/Mamba%E6%9E%B6%E6%9E%84/1.htm">Mamba架构</a><a class="tag" taget="_blank" href="/search/AI%E5%A4%A7%E6%A8%A1%E5%9E%8B%E7%B3%BB%E7%BB%9F%E5%BC%80%E5%8F%91%E5%AE%9E%E6%88%98/1.htm">AI大模型系统开发实战</a><a class="tag" taget="_blank" href="/search/AI%E5%A4%A7%E6%A8%A1%E5%9E%8B%E9%AB%98%E6%89%8B%E5%BC%80%E5%8F%91/1.htm">AI大模型高手开发</a><a class="tag" taget="_blank" href="/search/AI%E5%A4%A7%E6%A8%A1%E5%9E%8B%E7%B3%BB%E7%BB%9F%E5%AE%9E%E6%88%98/1.htm">AI大模型系统实战</a> <div>Transformer架构自2017年诞生以来，一直是NLP、计算机视觉等领域的“统治级”模型架构。但随着序列长度需求的增长（如128K长文本处理、基因组学超长序列分析），其自注意力机制的O(n2)O(n^2)O(n2)计算复杂度成为难以逾越的瓶颈。2023年底，由AlbertGu和TriDao等人提出的Mamba架构，通过创新的“选择性状态空间模型（SelectiveSSM）”实现了线性复杂度（</div> </li> <li><a href="/article/1949882676047572992.htm" title="Llama 2 模型架构深度解析：Transformer的进化" target="_blank">Llama 2 模型架构深度解析：Transformer的进化</a> SuperAGI架构师的AI实验室 <a class="tag" taget="_blank" href="/search/AI%E5%A4%A7%E6%A8%A1%E5%9E%8B%E5%BA%94%E7%94%A8%E5%BC%80%E5%8F%91%E5%AE%9D%E5%85%B8/1.htm">AI大模型应用开发宝典</a><a class="tag" taget="_blank" href="/search/llama/1.htm">llama</a><a class="tag" taget="_blank" href="/search/%E6%9E%B6%E6%9E%84/1.htm">架构</a><a class="tag" taget="_blank" href="/search/transformer/1.htm">transformer</a><a class="tag" taget="_blank" href="/search/ai/1.htm">ai</a> <div>Llama2模型架构深度解析：Transformer的进化关键词：Llama2、Transformer、模型架构、进化、人工智能摘要：本文将深入剖析Llama2的模型架构，探讨它作为Transformer进化版本的独特之处。从背景知识的介绍，到核心概念的解释，再到算法原理、实战案例以及实际应用场景等方面，为读者全面展现Llama2的魅力和价值。通过通俗易懂的语言，让即使是对技术不太熟悉的读者也能理</div> </li> <li><a href="/article/1949724438018715648.htm" title="【Python】Python+sentence-transformers框架实现相似文本识别" target="_blank">【Python】Python+sentence-transformers框架实现相似文本识别</a> 宅男很神经 <a class="tag" taget="_blank" href="/search/python/1.htm">python</a><a class="tag" taget="_blank" href="/search/%E5%BC%80%E5%8F%91%E8%AF%AD%E8%A8%80/1.htm">开发语言</a> <div>第一章：文本相似度与语义表示概述在深入sentence-transformers框架之前，我们首先需要对文本相似度计算及其背后的核心概念——语义表示，有一个清晰且全面的理解。这构成了后续所有讨论的基础。1.1什么是文本相似度？1.1.1定义与重要性文本相似度（TextSimilarity）是指衡量两段文本（可以是词、短语、句子、段落或整个文档）在意义或内容上相近程度的指标。这种相近可以是字面上的（</div> </li> <li><a href="/article/1949690768637620224.htm" title="揭秘Transformer架构：残差流与隐藏层的关系" target="_blank">揭秘Transformer架构：残差流与隐藏层的关系</a> ZhangJiQun&MXP <a class="tag" taget="_blank" href="/search/%E6%95%99%E5%AD%A6/1.htm">教学</a><a class="tag" taget="_blank" href="/search/2024%E5%A4%A7%E6%A8%A1%E5%9E%8B%E4%BB%A5%E5%8F%8A%E7%AE%97%E5%8A%9B/1.htm">2024大模型以及算力</a><a class="tag" taget="_blank" href="/search/2021/1.htm">2021</a><a class="tag" taget="_blank" href="/search/AI/1.htm">AI</a><a class="tag" taget="_blank" href="/search/python/1.htm">python</a><a class="tag" taget="_blank" href="/search/transformer/1.htm">transformer</a><a class="tag" taget="_blank" href="/search/%E6%B7%B1%E5%BA%A6%E5%AD%A6%E4%B9%A0/1.htm">深度学习</a><a class="tag" taget="_blank" href="/search/%E4%BA%BA%E5%B7%A5%E6%99%BA%E8%83%BD/1.htm">人工智能</a><a class="tag" taget="_blank" href="/search/linux/1.htm">linux</a><a class="tag" taget="_blank" href="/search/%E7%AE%97%E6%B3%95/1.htm">算法</a> <div>在Transformer架构的LLM中，“残差流”（residualstream）和“隐藏层”（hiddenlayers）是密切相关但不同的概念，前者是层间流动的核心数据，后者是处理这些数据的结构单元。1.残差流（ResidualStream）：层间传递的“信息流”残差流指的是在Transformer层之间传递的核心张量，它是模型中“流动”的数据载体。其本质是通过“残差连接”（residualco</div> </li> <li><a href="/article/1949598357651517440.htm" title="【代码问题】【模型部署】部署千问时，ImportError: Cannot import available module of Qwen2_5_VLForConditionalGeneration" target="_blank">【代码问题】【模型部署】部署千问时，ImportError: Cannot import available module of Qwen2_5_VLForConditionalGeneration</a> Catching Star <a class="tag" taget="_blank" href="/search/python/1.htm">python</a><a class="tag" taget="_blank" href="/search/pytorch/1.htm">pytorch</a><a class="tag" taget="_blank" href="/search/%E5%BC%80%E5%8F%91%E8%AF%AD%E8%A8%80/1.htm">开发语言</a> <div>多半是环境的问题，最主要的是python版本要高python==3.12.9accelerate==1.8.1pipinstallqwen-vl-utils[decord]==0.0.8peft==0.14.0transformers==4.52.3torch==2.7.0torchvision==0.22.0modelscope==1.27.1</div> </li> <li><a href="/article/1949586627332468736.htm" title="Kettle8.2ETL项目实战教程：快速掌握数据整合利器，提升数据处理效率" target="_blank">Kettle8.2ETL项目实战教程：快速掌握数据整合利器，提升数据处理效率</a> <div>Kettle8.2ETL项目实战教程：快速掌握数据整合利器，提升数据处理效率去发现同类优质开源项目:https://gitcode.com/Kettle8.2ETL项目实战教程，帮助您轻松学习ETL基本流程，高效整合各种数据源，实现数据转换与输出。项目介绍在现代数据分析和大数据处理中，ETL（Extract,Transform,Load）技术扮演着至关重要的角色。Kettle8.2ETL项目实战教</div> </li> <li><a href="/article/1949553348961169408.htm" title="伪类选择器:root的妙用" target="_blank">伪类选择器:root的妙用</a> weixin_33921089 <a class="tag" taget="_blank" href="/search/javascript/1.htm">javascript</a><a class="tag" taget="_blank" href="/search/ViewUI/1.htm">ViewUI</a> <div>css3的元素旋转功能非常强大，也非常吸引人，但是很多时候因为浏览器使用率的问题，我们必需要想办法兼容一些低版本的浏览器，特别是ie这朵奇葩。想要实现元素旋转本来很简单的一个属性就能实现，那就是transform:rotate(xxdeg)。举个例子：实现一个层旋转270deg。#demo{width:300px;height:200px;background-color:#FF80C0;marg</div> </li> <li><a href="/article/1949418560820408320.htm" title="XSLT：XML转换的“魔法棒”" target="_blank">XSLT：XML转换的“魔法棒”</a> 星语卿 <a class="tag" taget="_blank" href="/search/windows/1.htm">windows</a> <div>大家好！今天我们来聊聊XSLT（ExtensibleStylesheetLanguageTransformations），一种用于转换和呈现XML文档的神奇工具。如果你曾需要将一堆枯燥的XML数据变成精美的HTML网页、PDF报告，或其他XML格式，XSLT就是你的“瑞士军刀”。一、XSLT是什么？XSLT是XML家族中的核心成员，专为数据转换而生。它的核心思想很简单：输入：一个XML文档（如订单</div> </li> <li><a href="/article/1949372413615599616.htm" title="人工智能自然语言处理：Transformer 模型详解" target="_blank">人工智能自然语言处理：Transformer 模型详解</a> 大力出奇迹985 <a class="tag" taget="_blank" href="/search/%E4%BA%BA%E5%B7%A5%E6%99%BA%E8%83%BD/1.htm">人工智能</a><a class="tag" taget="_blank" href="/search/%E8%87%AA%E7%84%B6%E8%AF%AD%E8%A8%80%E5%A4%84%E7%90%86/1.htm">自然语言处理</a><a class="tag" taget="_blank" href="/search/transformer/1.htm">transformer</a> <div>一、Transformer模型的诞生背景在自然语言处理的漫长征程中，早期的传统模型，如循环神经网络（RNN）及其变体长短时记忆网络（LSTM），曾占据主导地位。RNN试图通过依次处理序列中的每个元素，来捕捉上下文信息。但它存在一个致命弱点，在处理长序列时，会面临梯度消失或梯度爆炸的问题，就像一个长途跋涉的旅人，随着路程的增加，逐渐忘记了出发时的目标和重要信息。LSTM虽然在一定程度上缓解了这个问题</div> </li> <li><a href="/article/1949368633633337344.htm" title="代码随想录算法训练营第五十三天|图论part4" target="_blank">代码随想录算法训练营第五十三天|图论part4</a> xindafu <a class="tag" taget="_blank" href="/search/%E5%9B%BE%E8%AE%BA/1.htm">图论</a> <div>110.字符串接龙题目链接：110.字符串接龙文章讲解：代码随想录思路：把每个字符串看成图的一个节点。转换为求无权图两节点的的最短路径。求最短路径用bfs#include#include#include#include#includeusingnamespacestd;unordered_mapmymap;boolcanTransform(stringa,stringb){intcount=0;i</div> </li> <li><a href="/article/1949344933450149888.htm" title="什么是 ELK/Grafana" target="_blank">什么是 ELK/Grafana</a> 元圆源 <a class="tag" taget="_blank" href="/search/elk/1.htm">elk</a><a class="tag" taget="_blank" href="/search/grafana/1.htm">grafana</a><a class="tag" taget="_blank" href="/search/jenkins/1.htm">jenkins</a> <div>ELKDataFlowinELKStack:Logstash(Collect&Transform)→Elasticsearch(Store&Search)→Kibana(Visualize)ElasticsearchExploreElasticsearchQueryDSLWhatisElasticsearch?Elastic(formerlyElasticsearch)isasuiteofopen</div> </li> <li><a href="/article/1949302196612952064.htm" title="UITableView上下拖动动画" target="_blank">UITableView上下拖动动画</a> 舒翱 <div>-(void)tableView:(UITableView*)tableViewwillDisplayCell:(UITableViewCell*)cellforRowAtIndexPath:(NSIndexPath*)indexPath{//1.配置CATransform3D的内容CATransform3Dtransform;transform=CATransform3DMakeRotation</div> </li> <li><a href="/article/1949273941243654144.htm" title="LightGBM+Transformer-LSTM多变量回归交通流量预测,附模型研究报告(Matlab)" target="_blank">LightGBM+Transformer-LSTM多变量回归交通流量预测,附模型研究报告(Matlab)</a> matlab科研助手 <a class="tag" taget="_blank" href="/search/transformer/1.htm">transformer</a><a class="tag" taget="_blank" href="/search/lstm/1.htm">lstm</a><a class="tag" taget="_blank" href="/search/%E5%9B%9E%E5%BD%92/1.htm">回归</a> <div>✅作者简介：热爱科研的Matlab仿真开发者，擅长数据处理、建模仿真、程序设计、完整代码获取、论文复现及科研仿真。往期回顾关注个人主页：Matlab科研工作室个人信条：格物致知,完整Matlab代码及仿真咨询内容私信。内容介绍交通流量预测作为智能交通系统（ITS）的核心组成部分，对城市规划、交通管理、交通诱导和出行决策具有至关重要的意义。准确、可靠的流量预测能够有效缓解交通拥堵，提高道路利用率，降</div> </li> <li><a href="/article/1949156410294071296.htm" title="ros2--tf2" target="_blank">ros2--tf2</a> 猿饵块 <a class="tag" taget="_blank" href="/search/ros2/1.htm">ros2</a><a class="tag" taget="_blank" href="/search/linux/1.htm">linux</a> <div>tf作用tf：transform，ROS中管理3D坐标系变换的工具，本质上就是一些库。用来发布两个坐标系的位姿变换关系，其他功能模块（比如RVIZ）可以通过查询TF的变换关系获取两个坐标系的实时位姿信息。RVIZ订阅TF变换TF变化的来源1，由gazebo仿真时，在URDF文件中指定发布TF变换，则仿真时就会不断发布TF话题数据；2，由真实机器人运动的驱动代码不断发布TF变换。RVIZ订阅TF数据</div> </li> <li><a href="/article/1949127297864888320.htm" title="AAAI 2024 | TMFormer：用于缺失模态脑肿瘤分割的令牌合并Transformer" target="_blank">AAAI 2024 | TMFormer：用于缺失模态脑肿瘤分割的令牌合并Transformer</a> 小白学视觉 <a class="tag" taget="_blank" href="/search/%E5%8C%BB%E5%AD%A6%E5%9B%BE%E5%83%8F%E5%A4%84%E7%90%86%E8%AE%BA%E6%96%87%E8%A7%A3%E8%AF%BB/1.htm">医学图像处理论文解读</a><a class="tag" taget="_blank" href="/search/transformer/1.htm">transformer</a><a class="tag" taget="_blank" href="/search/%E6%B7%B1%E5%BA%A6%E5%AD%A6%E4%B9%A0/1.htm">深度学习</a><a class="tag" taget="_blank" href="/search/%E4%BA%BA%E5%B7%A5%E6%99%BA%E8%83%BD/1.htm">人工智能</a><a class="tag" taget="_blank" href="/search/AAAI/1.htm">AAAI</a><a class="tag" taget="_blank" href="/search/%E8%AE%BA%E6%96%87%E8%A7%A3%E8%AF%BB/1.htm">论文解读</a><a class="tag" taget="_blank" href="/search/%E8%AE%A1%E7%AE%97%E6%9C%BA%E9%A1%B6%E4%BC%9A/1.htm">计算机顶会</a> <div>论文信息题目：TMFormer:TokenMergingTransformerforBrainTumorSegmentationwithMissingModalitiesTMFormer：用于缺失模态脑肿瘤分割的令牌合并Transformer作者：ZheyuZhang,GangYang,YueyiZhang,HuanjingYue,AipingLiu,YunweiOu,JianGong,Xiaoy</div> </li> <li><a href="/article/1949077852037115904.htm" title="【AIGC调研系列】敢于挑战Transformer的新架构Megalodon有什么优势" target="_blank">【AIGC调研系列】敢于挑战Transformer的新架构Megalodon有什么优势</a> Zachary AI <a class="tag" taget="_blank" href="/search/AIGC%E8%B0%83%E7%A0%94%E7%9B%B8%E5%85%B3/1.htm">AIGC调研相关</a><a class="tag" taget="_blank" href="/search/AIGC/1.htm">AIGC</a><a class="tag" taget="_blank" href="/search/transformer/1.htm">transformer</a><a class="tag" taget="_blank" href="/search/%E6%9E%B6%E6%9E%84/1.htm">架构</a> <div>Megalodon作为一种新架构，其优势主要体现在以下几个方面：无限上下文处理能力：Megalodon能够处理无限上下文，这一点在多个证据中得到了强调[1][2][3]。这意味着它能够在处理长文本时保持高效和准确，而不会因为上下文长度的限制而降低性能。高性能：在2万亿token的训练任务中，Megalodon的性能超越了Llama2-7B，实现了非凡的效率[1][2][3]。这表明Megalodo</div> </li> <li><a href="/article/1949077348196347904.htm" title="大模型系列——长度外推" target="_blank">大模型系列——长度外推</a> confiself <a class="tag" taget="_blank" href="/search/%E6%B7%B1%E5%BA%A6%E5%AD%A6%E4%B9%A0/1.htm">深度学习</a> <div>1.长度外推存在的问题1.长度外推存在不能识别的2.长度外推存在熵变问题3.长度内插入存在缩小距离分布2.直接使用外推技巧1.窗口局部关注+最终输出全局注意2.熵变+✖系数3.keynorm，增加模型识别距离能力4.增加bias，类似于SandwichTransformer升级之路：16、“复盘”长度外推技术</div> </li> <li><a href="/article/1949069527388057600.htm" title="RoPE：相对位置编码的旋转革命——原理、演进与大模型应用全景" target="_blank">RoPE：相对位置编码的旋转革命——原理、演进与大模型应用全景</a> 大千AI助手 <a class="tag" taget="_blank" href="/search/%E4%BA%BA%E5%B7%A5%E6%99%BA%E8%83%BD/1.htm">人工智能</a><a class="tag" taget="_blank" href="/search/Python/1.htm">Python</a><a class="tag" taget="_blank" href="/search/%23/1.htm">#</a><a class="tag" taget="_blank" href="/search/OTHER/1.htm">OTHER</a><a class="tag" taget="_blank" href="/search/%E4%BA%BA%E5%B7%A5%E6%99%BA%E8%83%BD/1.htm">人工智能</a><a class="tag" taget="_blank" href="/search/%E6%B7%B1%E5%BA%A6%E5%AD%A6%E4%B9%A0/1.htm">深度学习</a><a class="tag" taget="_blank" href="/search/%E5%A4%A7%E6%A8%A1%E5%9E%8B/1.htm">大模型</a><a class="tag" taget="_blank" href="/search/%E7%AE%97%E6%B3%95/1.htm">算法</a><a class="tag" taget="_blank" href="/search/RoPE/1.htm">RoPE</a><a class="tag" taget="_blank" href="/search/%E4%BD%8D%E7%BD%AE%E7%BC%96%E7%A0%81/1.htm">位置编码</a><a class="tag" taget="_blank" href="/search/%E7%9B%B8%E5%AF%B9%E4%BD%8D%E7%BD%AE/1.htm">相对位置</a> <div>“以复数旋转解锁位置关系的本质表达，让Transformer突破长度藩篱”旋转位置编码（RotaryPositionEmbedding,RoPE）是由JianlinSu等研究者于2021年提出的突破性位置编码方法，通过复数空间中的旋转操作将相对位置信息融入Transformer的自注意力机制，解决了传统位置编码在长序列建模中的外推瓶颈。该方法是当前主流大模型（如LLaMA、GPT-NeoX）的核心</div> </li> <li><a href="/article/1949054777342095360.htm" title="浅谈生成式AI语言模型的现状与展望" target="_blank">浅谈生成式AI语言模型的现状与展望</a> <div>摘要生成式人工智能语言模型作为当前人工智能领域最具突破性的技术之一，正在深刻改变着自然语言处理的技术范式和应用格局。本文从学术文献综述的角度，系统梳理了从Transformer架构到大语言模型的技术演进历程，深入分析了当前生成式AI语言模型的核心技术特征、应用现状以及面临的主要挑战，并展望了未来发展趋势。研究表明，生成式AI语言模型在参数规模扩展、多模态融合、推理能力提升等方面取得了显著进展，但仍</div> </li> <li><a href="/article/1948984173259714560.htm" title="Transformer：颠覆NLP的自注意力革命" target="_blank">Transformer：颠覆NLP的自注意力革命</a> ZhangJiQun&MXP <a class="tag" taget="_blank" href="/search/%E6%95%99%E5%AD%A6/1.htm">教学</a><a class="tag" taget="_blank" href="/search/2024%E5%A4%A7%E6%A8%A1%E5%9E%8B%E4%BB%A5%E5%8F%8A%E7%AE%97%E5%8A%9B/1.htm">2024大模型以及算力</a><a class="tag" taget="_blank" href="/search/2021/1.htm">2021</a><a class="tag" taget="_blank" href="/search/AI/1.htm">AI</a><a class="tag" taget="_blank" href="/search/python/1.htm">python</a><a class="tag" taget="_blank" href="/search/transformer/1.htm">transformer</a><a class="tag" taget="_blank" href="/search/%E8%87%AA%E7%84%B6%E8%AF%AD%E8%A8%80%E5%A4%84%E7%90%86/1.htm">自然语言处理</a><a class="tag" taget="_blank" href="/search/%E6%B7%B1%E5%BA%A6%E5%AD%A6%E4%B9%A0/1.htm">深度学习</a> <div>Transformer：颠覆NLP的自注意力革命Transformer是自然语言处理领域中极具影响力的深度学习模型架构，以下是对其的详细介绍：提出背景与应用：2017年，Vaswani等人在《AttentionIsAllYouNeed》论文中首次提出Transformer架构，它主要用于处理序列到序列的任务，如机器翻译、文本生成等。核心原理：文本生成的Transformer模型原理是“预测下一个词</div> </li> <li><a href="/article/1948981275180199936.htm" title="Pytorch实现细节解析：Transformer模型的Encoder与Decoder逐行代码讲解" target="_blank">Pytorch实现细节解析：Transformer模型的Encoder与Decoder逐行代码讲解</a> lazycatlove <a class="tag" taget="_blank" href="/search/pytorch/1.htm">pytorch</a><a class="tag" taget="_blank" href="/search/transformer/1.htm">transformer</a><a class="tag" taget="_blank" href="/search/%E4%BA%BA%E5%B7%A5%E6%99%BA%E8%83%BD/1.htm">人工智能</a> <div>文章目录摘要一、Transformer1.1为什么要使用attention1.2Transformer的优点二、Transformer模型Encoder和Decoder原理讲解与其Pytorch逐行实现2.1wordembedding2.2单词索引构成源句子和目标句子2.3构建positionembedding2.4构造encoder的self-attentionmask2.5构造intra-at</div> </li> <li><a href="/article/1948979255249530880.htm" title="Swin Transformer原理与代码精讲" target="_blank">Swin Transformer原理与代码精讲</a> bai666ai <a class="tag" taget="_blank" href="/search/%E6%B7%B1%E5%BA%A6%E5%AD%A6%E4%B9%A0%E4%B9%8B%E8%AE%A1%E7%AE%97%E6%9C%BA%E8%A7%86%E8%A7%89/1.htm">深度学习之计算机视觉</a><a class="tag" taget="_blank" href="/search/transformer/1.htm">transformer</a><a class="tag" taget="_blank" href="/search/swin/1.htm">swin</a><a class="tag" taget="_blank" href="/search/CV/1.htm">CV</a><a class="tag" taget="_blank" href="/search/%E6%B7%B1%E5%BA%A6%E5%AD%A6%E4%B9%A0/1.htm">深度学习</a><a class="tag" taget="_blank" href="/search/%E5%9B%BE%E5%83%8F%E5%88%86%E7%B1%BB/1.htm">图像分类</a> <div>课程链接：SwinTransformer原理与代码精讲--计算机视觉视频教程-人工智能-CSDN程序员研修院Transformer在许多NLP(自然语言处理)任务中取得了最先进的成果。SwinTransformer是在ViT基础上发展而来，是Transformer应用于CV（计算机视觉）领域又一里程碑式的工作。它可以作为通用的骨干网络，用于图片分类的CV任务，以及下游的CV任务，如目标检测、实例分</div> </li> <li><a href="/article/1948976608551432192.htm" title="Transformer Masked loss原理精讲及其PyTorch逐行实现" target="_blank">Transformer Masked loss原理精讲及其PyTorch逐行实现</a> <div>MaskedLoss的核心原理是：在计算损失函数时，只考虑真实有意义的词元（token），而忽略掉为了数据对齐而填充的无意义的填充词元（paddingtoken）。这是重要的技术，可以确保模型专注于学习有意义的任务，并得到一个正确的性能评估。1.原理精讲为什么需要MaskedLoss？在训练神经网络时，我们通常会用一个批次（batch）的数据进行训练，而不是一次只用一个样本。对于自然语言处理任务，</div> </li> <li><a href="/article/1948975851555057664.htm" title="深入探讨 Transformer 模型架构" target="_blank">深入探讨 Transformer 模型架构</a> 年纪轻轻头已凉 <a class="tag" taget="_blank" href="/search/transformer/1.htm">transformer</a><a class="tag" taget="_blank" href="/search/%E6%B7%B1%E5%BA%A6%E5%AD%A6%E4%B9%A0/1.htm">深度学习</a><a class="tag" taget="_blank" href="/search/%E4%BA%BA%E5%B7%A5%E6%99%BA%E8%83%BD/1.htm">人工智能</a> <div>```html深入探讨Transformer模型架构深入探讨Transformer模型架构Transformer是一种革命性的神经网络架构，由Vaswani等人在2017年提出，并在自然语言处理（NLP）领域取得了显著的成功。与传统的循环神经网络（RNN）和卷积神经网络（CNN）不同，Transformer完全依赖于自注意力机制（Self-AttentionMechanism），这使得它在处理长序</div> </li> <li><a href="/article/1948973960351772672.htm" title="LLM面试题详解：拿到大厂Offer" target="_blank">LLM面试题详解：拿到大厂Offer</a> ZhangJiQun&MXP <a class="tag" taget="_blank" href="/search/%E6%95%99%E5%AD%A6/1.htm">教学</a><a class="tag" taget="_blank" href="/search/2024%E5%A4%A7%E6%A8%A1%E5%9E%8B%E4%BB%A5%E5%8F%8A%E7%AE%97%E5%8A%9B/1.htm">2024大模型以及算力</a><a class="tag" taget="_blank" href="/search/2021/1.htm">2021</a><a class="tag" taget="_blank" href="/search/AI/1.htm">AI</a><a class="tag" taget="_blank" href="/search/python/1.htm">python</a><a class="tag" taget="_blank" href="/search/transformer/1.htm">transformer</a><a class="tag" taget="_blank" href="/search/%E6%B7%B1%E5%BA%A6%E5%AD%A6%E4%B9%A0/1.htm">深度学习</a><a class="tag" taget="_blank" href="/search/%E4%BA%BA%E5%B7%A5%E6%99%BA%E8%83%BD/1.htm">人工智能</a> <div>LLM面试题核心架构与基本概念Token化包含哪些内容，为什么它对LLM至关重要？Token化是将文本分解为更小单元（如单词、词的一部分或字符）的过程。它对LLM至关重要，因为LLM处理的是token的数值版本，通过Token化，模型可以处理多种语言、稀有词汇，保持词汇表大小可管理，提高计算速度和模型有效性。注意力机制在Transformer模型中如何运作？注意力机制通过计算查询（query）、键</div> </li> <li><a href="/article/98.htm" title="微信开发者验证接口开发" target="_blank">微信开发者验证接口开发</a> 362217990 <a class="tag" taget="_blank" href="/search/%E5%BE%AE%E4%BF%A1+%E5%BC%80%E5%8F%91%E8%80%85+token+%E9%AA%8C%E8%AF%81/1.htm">微信开发者 token 验证</a> <div>微信开发者接口验证。 Token，自己随便定义，与微信填写一致就可以了。根据微信接入指南描述 http://mp.weixin.qq.com/wiki/17/2d4265491f12608cd170a95559800f2d.html 第一步：填写服务器配置第二步：验证服务器地址的有效性第三步：依据接口文档实现业务逻辑这里主要讲第二步验证服务器有效性。建一个</div> </li> <li><a href="/article/225.htm" title="一个小编程题-类似约瑟夫环问题" target="_blank">一个小编程题-类似约瑟夫环问题</a> BrokenDreams <a class="tag" taget="_blank" href="/search/%E7%BC%96%E7%A8%8B/1.htm">编程</a> <div> 今天群友出了一题：一个数列,把第一个元素删除,然后把第二个元素放到数列的最后,依次操作下去,直到把数列中所有的数都删除,要求依次打印出这个过程中删除的数。 &</div> </li> <li><a href="/article/352.htm" title="linux复习笔记之bash shell (5) 关于减号-的作用" target="_blank">linux复习笔记之bash shell (5) 关于减号-的作用</a> eksliang <a class="tag" taget="_blank" href="/search/linux%E5%85%B3%E4%BA%8E%E5%87%8F%E5%8F%B7%E2%80%9C-%E2%80%9D%E7%9A%84%E5%90%AB%E4%B9%89/1.htm">linux关于减号“-”的含义</a><a class="tag" taget="_blank" href="/search/linux%E5%85%B3%E4%BA%8E%E5%87%8F%E5%8F%B7%E2%80%9C-%E2%80%9D%E7%9A%84%E7%94%A8%E9%80%94/1.htm">linux关于减号“-”的用途</a><a class="tag" taget="_blank" href="/search/linux%E5%85%B3%E4%BA%8E%E2%80%9C-%E2%80%9D%E7%9A%84%E5%90%AB%E4%B9%89/1.htm">linux关于“-”的含义</a><a class="tag" taget="_blank" href="/search/linux%E5%85%B3%E4%BA%8E%E5%87%8F%E5%8F%B7%E7%9A%84%E5%90%AB%E4%B9%89/1.htm">linux关于减号的含义</a> <div> 转载请出自出处： http://eksliang.iteye.com/blog/2105677 管道命令在bash的连续处理程序中是相当重要的，尤其在使用到前一个命令的studout（标准输出）作为这次的stdin（标准输入）时，就显得太重要了，某些命令需要用到文件名，例如上篇文档的的切割命令（split）、还有</div> </li> <li><a href="/article/479.htm" title="Unix(3)" target="_blank">Unix(3)</a> 18289753290 <a class="tag" taget="_blank" href="/search/unix+ksh/1.htm">unix ksh</a> <div>1)若该变量需要在其他子进程执行，则可用"$变量名称"或${变量}累加内容什么是子进程？在我目前这个shell情况下，去打开一个新的shell，新的那个shell就是子进程。一般状态下，父进程的自定义变量是无法在子进程内使用的，但通过export将变量变成环境变量后就能够在子进程里面应用了。 2)条件判断： &&代表and ||代表or&nbs</div> </li> <li><a href="/article/606.htm" title="关于ListView中性能优化中图片加载问题" target="_blank">关于ListView中性能优化中图片加载问题</a> 酷的飞上天空 <a class="tag" taget="_blank" href="/search/ListView/1.htm">ListView</a> <div>ListView的性能优化网上很多信息，但是涉及到异步加载图片问题就会出现问题。具体参看上篇文章http://314858770.iteye.com/admin/blogs/1217594 如果每次都重新inflate一个新的View出来肯定会造成性能损失严重，可能会出现listview滚动是很卡的情况，还会出现内存溢出。现在想出一个方法就是每次都添加一个标识，然后设置图</div> </li> <li><a href="/article/733.htm" title="德国总理默多克：给国人的一堂“震撼教育”课" target="_blank">德国总理默多克：给国人的一堂“震撼教育”课</a> 永夜-极光 <a class="tag" taget="_blank" href="/search/%E6%95%99%E8%82%B2/1.htm">教育</a> <div>http://bbs.voc.com.cn/topic-2443617-1-1.html德国总理默多克：给国人的一堂“震撼教育”课　安吉拉—默克尔，一位经历过社会主义的东德人，她利用自己的博客，发表一番来华前的谈话，该说的话，都在上面说了，全世界想看想传播——去看看默克尔总理的博客吧！　　德国总理默克尔以她的低调、朴素、谦和、平易近人等品格给国人留下了深刻印象。她以实际行动为中国人上了一堂</div> </li> <li><a href="/article/860.htm" title="关于Java继承的一个小问题。。。" target="_blank">关于Java继承的一个小问题。。。</a> 随便小屋 <a class="tag" taget="_blank" href="/search/java/1.htm">java</a> <div>今天看Java 编程思想的时候遇见一个问题，运行的结果和自己想想的完全不一样。先把代码贴出来！ //CanFight接口 interface Canfight { void fight(); } //ActionCharacter类 class ActionCharacter { public void fight() { System.out.pr</div> </li> <li><a href="/article/987.htm" title="23种基本的设计模式" target="_blank">23种基本的设计模式</a> aijuans <a class="tag" taget="_blank" href="/search/%E8%AE%BE%E8%AE%A1%E6%A8%A1%E5%BC%8F/1.htm">设计模式</a> <div>Abstract Factory：提供一个创建一系列相关或相互依赖对象的接口，而无需指定它们具体的类。　　Adapter：将一个类的接口转换成客户希望的另外一个接口。A d a p t e r模式使得原本由于接口不兼容而不能一起工作的那些类可以一起工作。　　Bridge：将抽象部分与它的实现部分分离，使它们都可以独立地变化。　　Builder：将一个复杂对象的构建与它的表示分离，使得同</div> </li> <li><a href="/article/1114.htm" title="《周鸿祎自述：我的互联网方法论》读书笔记" target="_blank">《周鸿祎自述：我的互联网方法论》读书笔记</a> aoyouzi <a class="tag" taget="_blank" href="/search/%E8%AF%BB%E4%B9%A6%E7%AC%94%E8%AE%B0/1.htm">读书笔记</a> <div>从用户的角度来看,能解决问题的产品才是好产品,能方便/快速地解决问题的产品,就是一流产品. 商业模式不是赚钱模式一款产品免费获得海量用户后,它的边际成本趋于0,然后再通过广告或者增值服务的方式赚钱,实际上就是创造了新的价值链. 商业模式的基础是用户,木有用户,任何商业模式都是浮云.商业模式的核心是产品,本质是通过产品为用户创造价值. 商业模式还包括寻找需求</div> </li> <li><a href="/article/1241.htm" title="JavaScript动态改变样式访问技术" target="_blank">JavaScript动态改变样式访问技术</a> 百合不是茶 <a class="tag" taget="_blank" href="/search/JavaScript/1.htm">JavaScript</a><a class="tag" taget="_blank" href="/search/style%E5%B1%9E%E6%80%A7/1.htm">style属性</a><a class="tag" taget="_blank" href="/search/ClassName%E5%B1%9E%E6%80%A7/1.htm">ClassName属性</a> <div> 一:style属性格式: HTML元素.style.样式属性="值"; 创建菜单:在html标签中创建或者在head标签中用数组创建 <html> <head> <title>style改变样式</title> </head> &l</div> </li> <li><a href="/article/1368.htm" title="jQuery的deferred对象详解" target="_blank">jQuery的deferred对象详解</a> bijian1013 <a class="tag" taget="_blank" href="/search/jquery/1.htm">jquery</a><a class="tag" taget="_blank" href="/search/deferred%E5%AF%B9%E8%B1%A1/1.htm">deferred对象</a> <div> jQuery的开发速度很快，几乎每半年一个大版本，每两个月一个小版本。每个版本都会引入一些新功能，从jQuery 1.5.0版本开始引入的一个新功能----deferred对象。 &nb</div> </li> <li><a href="/article/1495.htm" title="淘宝开放平台TOP" target="_blank">淘宝开放平台TOP</a> Bill_chen <a class="tag" taget="_blank" href="/search/C%2B%2B/1.htm">C++</a><a class="tag" taget="_blank" href="/search/c/1.htm">c</a><a class="tag" taget="_blank" href="/search/%E7%89%A9%E6%B5%81/1.htm">物流</a><a class="tag" taget="_blank" href="/search/C%23/1.htm">C#</a> <div>淘宝网开放平台首页：http://open.taobao.com/ 淘宝开放平台是淘宝TOP团队的产品，TOP即TaoBao Open Platform，是淘宝合作伙伴开发、发布、交易其服务的平台。支撑TOP的三条主线为： 1.开放数据和业务流程 * 以API数据形式开放商品、交易、物流等业务； &</div> </li> <li><a href="/article/1622.htm" title="【大型网站架构一】大型网站架构概述" target="_blank">【大型网站架构一】大型网站架构概述</a> bit1129 <a class="tag" taget="_blank" href="/search/%E7%BD%91%E7%AB%99%E6%9E%B6%E6%9E%84/1.htm">网站架构</a> <div>大型互联网特点面对海量用户、海量数据大型互联网架构的关键指标高并发高性能高可用高可扩展性线性伸缩性安全性大型互联网技术要点前端优化 CDN缓存反向代理 KV缓存消息系统分布式存储 NoSQL数据库搜索监控安全想到的问题： 1.对于订单系统这种事务型系统，如</div> </li> <li><a href="/article/1749.htm" title="eclipse插件hibernate tools安装" target="_blank">eclipse插件hibernate tools安装</a> 白糖_ <a class="tag" taget="_blank" href="/search/Hibernate/1.htm">Hibernate</a> <div> eclipse helios(3.6)版 1.启动eclipse 2.选择 Help > Install New Software...> 3.添加如下地址： http://download.jboss.org/jbosstools/updates/stable/helios/ 4.选择性安装：hibernate tools在All Jboss tool</div> </li> <li><a href="/article/1876.htm" title="Jquery easyui Form表单提交注意事项" target="_blank">Jquery easyui Form表单提交注意事项</a> bozch <a class="tag" taget="_blank" href="/search/jquery+easyui/1.htm">jquery easyui</a> <div>jquery easyui对表单的提交进行了封装，提交的方式采用的是ajax的方式，在开发的时候应该注意的事项如下： 1、在定义form标签的时候，要将method属性设置成post或者get，特别是进行大字段的文本信息提交的时候，要将method设置成post方式提交，否则页面会抛出跨域访问等异常。所以这个要</div> </li> <li><a href="/article/2003.htm" title="Trie tree(字典树)的Java实现及其应用-统计以某字符串为前缀的单词的数量" target="_blank">Trie tree(字典树)的Java实现及其应用-统计以某字符串为前缀的单词的数量</a> bylijinnan <a class="tag" taget="_blank" href="/search/java%E5%AE%9E%E7%8E%B0/1.htm">java实现</a> <div> import java.util.LinkedList; public class CaseInsensitiveTrie { /** 字典树的Java实现。实现了插入、查询以及深度优先遍历。 Trie tree's java implementation.(Insert,Search,DFS) Problem Description Igna</div> </li> <li><a href="/article/2130.htm" title="html css 鼠标形状样式汇总" target="_blank">html css 鼠标形状样式汇总</a> chenbowen00 <a class="tag" taget="_blank" href="/search/html/1.htm">html</a><a class="tag" taget="_blank" href="/search/css/1.htm">css</a> <div>css鼠标手型cursor中hand与pointer Example：CSS鼠标手型效果 <a href="#" style="cursor:hand">CSS鼠标手型效果</a> Example：CSS鼠标手型效果 <a href="#" style=&qu</div> </li> <li><a href="/article/2257.htm" title="[IT与投资]IT投资的几个原则" target="_blank">[IT与投资]IT投资的几个原则</a> comsci <a class="tag" taget="_blank" href="/search/it/1.htm">it</a> <div> 无论是想在电商,软件,硬件还是互联网领域投资,都需要大量资金,虽然各个国家政府在媒体上都给予大家承诺,既要让市场的流动性宽松,又要保持经济的高速增长....但是,事实上,整个市场和社会对于真正的资金投入是非常渴望的,也就是说,表面上看起来,市场很活跃,但是投入的资金并不是很充足的...... </div> </li> <li><a href="/article/2384.htm" title="oracle with语句详解" target="_blank">oracle with语句详解</a> daizj <a class="tag" taget="_blank" href="/search/oracle/1.htm">oracle</a><a class="tag" taget="_blank" href="/search/with/1.htm">with</a><a class="tag" taget="_blank" href="/search/with+as/1.htm">with as</a> <div>oracle with语句详解转在oracle中，select 查询语句，可以使用with,就是一个子查询，oracle 会把子查询的结果放到临时表中，可以反复使用例子:注意，这是sql语句，不是pl/sql语句，可以直接放到jdbc执行的 ----------------------------------------------------------------</div> </li> <li><a href="/article/2511.htm" title="hbase的简单操作" target="_blank">hbase的简单操作</a> deng520159 <a class="tag" taget="_blank" href="/search/%E6%95%B0%E6%8D%AE%E5%BA%93/1.htm">数据库</a><a class="tag" taget="_blank" href="/search/hbase/1.htm">hbase</a> <div>近期公司用hbase来存储日志,然后再来分析 ,把hbase开发经常要用的命令找了出来. 用ssh登陆安装hbase那台linux后用hbase shell进行hbase命令控制台! 表的管理 1）查看有哪些表 hbase(main)> list 2）创建表 # 语法：create <table>, {NAME => <family&g</div> </li> <li><a href="/article/2638.htm" title="C语言scanf继续学习、算术运算符学习和逻辑运算符" target="_blank">C语言scanf继续学习、算术运算符学习和逻辑运算符</a> dcj3sjt126com <a class="tag" taget="_blank" href="/search/c/1.htm">c</a> <div>/* 2013年3月11日20:37:32 地点：北京潘家园功能：完成用户格式化输入多个值目的：学习scanf函数的使用 */ # include <stdio.h> int main(void) { int i, j, k; printf("please input three number:\n"); //提示用</div> </li> <li><a href="/article/2765.htm" title="2015越来越好" target="_blank">2015越来越好</a> dcj3sjt126com <a class="tag" taget="_blank" href="/search/%E6%AD%8C%E6%9B%B2/1.htm">歌曲</a> <div>越来越好房子大了电话小了感觉越来越好假期多了收入高了工作越来越好商品精了价格活了心情越来越好天更蓝了水更清了环境越来越好活得有奔头人会步步高想做到你要努力去做到幸福的笑容天天挂眉梢越来越好婆媳和了家庭暖了生活越来越好孩子高了懂事多了学习越来越好朋友多了心相通了大家越来越好道路宽了心气顺了日子越来越好活的有精神人就不显</div> </li> <li><a href="/article/2892.htm" title="java.sql.SQLException: Value '0000-00-00' can not be represented as java.sql.Tim" target="_blank">java.sql.SQLException: Value '0000-00-00' can not be represented as java.sql.Tim</a> feiteyizu <a class="tag" taget="_blank" href="/search/mysql/1.htm">mysql</a> <div>数据表中有记录的time字段（属性为timestamp）其值为：“0000-00-00 00:00:00” 程序使用select 语句从中取数据时出现以下异常： java.sql.SQLException:Value '0000-00-00' can not be represented as java.sql.Date java.sql.SQLException: Valu</div> </li> <li><a href="/article/3019.htm" title="Ehcache（07）——Ehcache对并发的支持" target="_blank">Ehcache（07）——Ehcache对并发的支持</a> 234390216 <a class="tag" taget="_blank" href="/search/%E5%B9%B6%E5%8F%91/1.htm">并发</a><a class="tag" taget="_blank" href="/search/ehcache/1.htm">ehcache</a><a class="tag" taget="_blank" href="/search/%E9%94%81/1.htm">锁</a><a class="tag" taget="_blank" href="/search/ReadLock/1.htm">ReadLock</a><a class="tag" taget="_blank" href="/search/WriteLock/1.htm">WriteLock</a> <div>Ehcache对并发的支持在高并发的情况下，使用Ehcache缓存时，由于并发的读与写，我们读的数据有可能是错误的，我们写的数据也有可能意外的被覆盖。所幸的是Ehcache为我们提供了针对于缓存元素Key的Read（读）、Write（写）锁。当一个线程获取了某一Key的Read锁之后，其它线程获取针对于同</div> </li> <li><a href="/article/3146.htm" title="mysql中blob,text字段的合成索引" target="_blank">mysql中blob,text字段的合成索引</a> jackyrong <a class="tag" taget="_blank" href="/search/mysql/1.htm">mysql</a> <div> 在mysql中，原来有一个叫合成索引的，可以提高blob,text字段的效率性能，但只能用在精确查询，核心是增加一个列，然后可以用md5进行散列，用散列值查找则速度快比如： create table abc(id varchar(10),context blog,hash_value varchar(40)); insert into abc(1,rep</div> </li> <li><a href="/article/3273.htm" title="逻辑运算与移位运算" target="_blank">逻辑运算与移位运算</a> latty <a class="tag" taget="_blank" href="/search/%E4%BD%8D%E8%BF%90%E7%AE%97/1.htm">位运算</a><a class="tag" taget="_blank" href="/search/%E9%80%BB%E8%BE%91%E8%BF%90%E7%AE%97/1.htm">逻辑运算</a> <div>源码：正数的补码与原码相同例+7 源码：00000111 补码：00000111 （用8位二进制表示一个数）负数的补码：符号位为1，其余位为该数绝对值的原码按位取反；然后整个数加1。 -7 源码： 10000111 ，其绝对值为00000111 取反加一：11111001 为-7补码已知一个数的补码，求原码的操作分两种情况：</div> </li> <li><a href="/article/3400.htm" title="利用XSD 验证XML文件" target="_blank">利用XSD 验证XML文件</a> newerdragon <a class="tag" taget="_blank" href="/search/java/1.htm">java</a><a class="tag" taget="_blank" href="/search/xml/1.htm">xml</a><a class="tag" taget="_blank" href="/search/xsd/1.htm">xsd</a> <div>XSD文件（XML Schema 语言也称作 XML Schema 定义（XML Schema Definition，XSD）。具体使用方法和定义请参看： http://www.w3school.com.cn/schema/index.asp java自jdk1.5以上新增了SchemaFactory类可以实现对XSD验证的支持，使用起来也很方便。以下代码可用在J</div> </li> <li><a href="/article/3527.htm" title="搭建 CentOS 6 服务器(12) - Samba" target="_blank">搭建 CentOS 6 服务器(12) - Samba</a> rensanning <a class="tag" taget="_blank" href="/search/centos/1.htm">centos</a> <div>（1）安装 # yum -y install samba Installed: samba.i686 0:3.6.9-169.el6_5 # pdbedit -a rensn new password:123456 retype new password:123456 …… （2）Home文件夹 # mkdir /etc</div> </li> <li><a href="/article/3654.htm" title="Learn Nodejs 01" target="_blank">Learn Nodejs 01</a> toknowme <a class="tag" taget="_blank" href="/search/nodejs/1.htm">nodejs</a> <div>（1）下载nodejs https://nodejs.org/download/ 选择相应的版本进行下载（2）安装nodejs 安装的方式比较多，请baidu下我这边下载的是“node-v0.12.7-linux-x64.tar.gz”这个版本（1）上传服务器（2）解压 tar -zxvf node-v0.12.</div> </li> <li><a href="/article/3781.htm" title="jquery控制自动刷新的代码举例" target="_blank">jquery控制自动刷新的代码举例</a> xp9802 <a class="tag" taget="_blank" href="/search/jquery/1.htm">jquery</a> <div>1、html内容部分复制代码代码示例: <div id='log_reload'> <select name="id_s" size="1"> <option value='2'>-2s-</option> <option value='3'>-3s-</option</div> </li> </ul> </div> </div> </div> <div> <div class="container"> <div class="indexes"> 按字母分类： <a href="/tags/A/1.htm" target="_blank">A</a><a href="/tags/B/1.htm" target="_blank">B</a><a href="/tags/C/1.htm" target="_blank">C</a><a href="/tags/D/1.htm" target="_blank">D</a><a href="/tags/E/1.htm" target="_blank">E</a><a href="/tags/F/1.htm" target="_blank">F</a><a href="/tags/G/1.htm" target="_blank">G</a><a href="/tags/H/1.htm" target="_blank">H</a><a href="/tags/I/1.htm" target="_blank">I</a><a href="/tags/J/1.htm" target="_blank">J</a><a href="/tags/K/1.htm" target="_blank">K</a><a href="/tags/L/1.htm" target="_blank">L</a><a href="/tags/M/1.htm" target="_blank">M</a><a href="/tags/N/1.htm" target="_blank">N</a><a href="/tags/O/1.htm" target="_blank">O</a><a href="/tags/P/1.htm" target="_blank">P</a><a href="/tags/Q/1.htm" target="_blank">Q</a><a href="/tags/R/1.htm" target="_blank">R</a><a href="/tags/S/1.htm" target="_blank">S</a><a href="/tags/T/1.htm" target="_blank">T</a><a href="/tags/U/1.htm" target="_blank">U</a><a href="/tags/V/1.htm" target="_blank">V</a><a href="/tags/W/1.htm" target="_blank">W</a><a href="/tags/X/1.htm" target="_blank">X</a><a href="/tags/Y/1.htm" target="_blank">Y</a><a href="/tags/Z/1.htm" target="_blank">Z</a><a href="/tags/0/1.htm" target="_blank">其他</a> </div> </div> </div> <footer id="footer" class="mb30 mt30"> <div class="container"> <div class="footBglm"> <a target="_blank" href="/">首页</a> - <a target="_blank" href="/custom/about.htm">关于我们</a> - <a target="_blank" href="/search/Java/1.htm">站内搜索</a> - <a target="_blank" href="/sitemap.txt">Sitemap</a> - <a target="_blank" href="/custom/delete.htm">侵权投诉</a> </div> <div class="copyright">版权所有 IT知识库 CopyRight © 2000-2050 E-COM-NET.COM , All Rights Reserved.  </div> </div> </footer>  <script type="text/javascript" src="/static/syntaxhighlighter/scripts/shCore.js"></script> <script type="text/javascript" src="/static/syntaxhighlighter/scripts/shLegacy.js"></script> <script type="text/javascript" src="/static/syntaxhighlighter/scripts/shAutoloader.js"></script> <link type="text/css" rel="stylesheet" href="/static/syntaxhighlighter/styles/shCoreDefault.css"/> <script type="text/javascript" src="/static/syntaxhighlighter/src/my_start_1.js"></script> </body> </html>

狼叔来找翻译人员了--plato--持续翻译中.....

目录