【WordPress插件】2022年最新版完整功能demo+插件v3.3.0 Not Nulled.zip

This project was bootstrapped with [Create Divi Extension](https://github.com/elegantthemes/create-divi-extension). Below you will find some information on how to perform common tasks. You can find the most recent version of this guide [here](https://github.com/elegantthemes/create-divi-extension/blob/master/packages/divi-scripts/template/README.md). ## Table of Contents - [Updating to New Releases](#updating-to-new-releases) - [Sending Feedback](#sending-feedback) - [Folder Structure](#folder-structure) - [Available Scripts](#available-scripts) - [yarn start](#yarn-start) - [yarn build](#yarn-build) - [yarn zip](#yarn-zip) - [yarn eject](#yarn-eject) - [Supported Browsers](#supported-browsers) - [Supported Language Features and Polyfills](#supported-language-features-and-polyfills) - [Syntax Highlighting in the Editor](#syntax-highlighting-in-the-editor) - [Displaying Lint Output in the Editor](#displaying-lint-output-in-the-editor) - [Debugging in the Editor](#debugging-in-the-editor) - [Formatting Code Automatically](#formatting-code-automatically) - [Installing a Dependency](#installing-a-dependency) - [Importing a Component](#importing-a-component) - [Adding a Stylesheet](#adding-a-stylesheet) - [Post-Processing CSS](#post-processing-css) - [Adding Flow](#adding-flow) - [Adding Custom Environment Variables](#adding-custom-environment-variables) - [Referencing Environment Variables in the HTML](#referencing-environment-variables-in-the-html) - [Adding Temporary Environment Variables In Your Shell](#adding-temporary-environment-variables-in-your-shell) - [Adding Development Environment Variables In `.env`](#adding-development-environment-variables-in-env) - [Can I Use Decorators?](#can-i-use-decorators) - [Fetching Data with AJAX Requests](#fetching-data-with-ajax-requests) - [Advanced Configuration](#advanced-configuration) - [Troubleshooting](#troubleshooting) - [`yarn start` doesn’t detect changes](#npm-start-doesnt-detect-changes) - [`yarn test` hangs on macOS Sierra](#npm-test-hangs-on-macos-sierra) - [`yarn build` exits too early](#npm-run-build-exits-too-early) - [`yarn build` fails to minify](#npm-run-build-fails-to-minify) - [Moment.js locales are missing](#momentjs-locales-are-missing) - [Alternatives to Ejecting](#alternatives-to-ejecting) - [Something Missing?](#something-missing) ## Updating to New Releases Create Divi Extension is divided into two packages: * `create-divi-extension` is a global command-line utility that you use to create new projects. * `divi-scripts` is a development dependency in the generated projects (including this one). You almost never need to update `create-divi-extension` itself: it delegates all the setup to `divi-scripts`. When you run `create-divi-extension`, it always creates the project with the latest version of `divi-scripts` so you’ll get all the new features and improvements in newly created extensions automatically. To update an existing project to a new version of `divi-scripts`, [open the changelog](https://github.com/elegantthemes/create-divi-extension/blob/master/CHANGELOG.md), find the version you’re currently on (check `package.json` in this folder if you’re not sure), and apply the migration instructions for the newer versions. In most cases bumping the `divi-scripts` version in `package.json` and running `npm install` in this folder should be enough, but it’s good to consult the [changelog](https://github.com/elegantthemes/create-divi-extension/blob/master/CHANGELOG.md) for potential breaking changes. We commit to keeping the breaking changes minimal so you can upgrade `divi-scripts` painlessly. ## Sending Feedback We are always open to [your feedback](https://github.com/elegantthemes/create-divi-extension/issues). ## Folder Structure After creation, your project should look like this: ``` my-extension ├── includes │   ├── modules │   │   └── HelloWorld │   │   ├── HelloWorld.jsx │   │   ├── HelloWorld.php │   │   └── style.css │   ├── loader.js │   ├── loader.php │   └── MyExtension.php ├── languages ├── node_modules ├── scripts │   └── frontend.js ├── styles ├── my-extension.php ├── package.json └── README.md ``` For the project to build, **these files must exist with exact filenames**: * `includes/loader.js` is the JavaScript entry point. You need to **put any JS and CSS files inside `includes`, `scripts`, and/or `styles`**, otherwise Webpack won’t see them. ## Available Scripts In the project directory, you can run: ### `yarn start` Builds the extension in the development mode. Open your WordPress site to view it in the browser. The page will reload if you make edits to JavaScript files. You will also see any lint errors in the console. ### `yarn build` Builds the extension for production to the `build` folder. It correctly optimizes the build for the best performance. ### `yarn zip` Runs `build` and then creates a production release zip file. ### `yarn eject` **Note: this is a one-way operation. Once you `eject`, you can’t go back!** If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project. Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own. You don’t have to ever use `eject`. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it. ## Supported Browsers By default, the generated project uses the latest version of React. You can refer [to the React documentation](https://reactjs.org/docs/react-dom.html#browser-support) for more information about supported browsers. ## Supported Language Features and Polyfills This project supports a superset of the latest JavaScript standard.<br> In addition to [ES6](https://github.com/lukehoban/es6features) syntax features, it also supports: * [Exponentiation Operator](https://github.com/rwaldron/exponentiation-operator) (ES2016) * [Async/await](https://github.com/tc39/ecmascript-asyncawait) (ES2017) * [Object Rest/Spread Properties](https://github.com/tc39/proposal-object-rest-spread) (ES2018) * [Dynamic import()](https://github.com/tc39/proposal-dynamic-import) (stage 3 proposal) * [Class Fields and Static Properties](https://github.com/tc39/proposal-class-public-fields) (stage 3 proposal) * [JSX](https://facebook.github.io/react/docs/introducing-jsx.html) syntax * [Flow](https://flowtype.org/) syntax Learn more about [different proposal stages](https://babeljs.io/docs/plugins/#presets-stage-x-experimental-presets-). While we recommend using experimental proposals with some caution, Facebook heavily uses these features in the product code, so they intend to provide [codemods](https://medium.com/@cpojer/effective-javascript-codemods-5a6686bb46fb) if any of these proposals change in the future. Note that **the project only includes a few ES6 [polyfills](https://en.wikipedia.org/wiki/Polyfill)**: * [`Object.assign()`](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Object/assign) via [`object-assign`](https://github.com/sindresorhus/object-assign). * [`Promise`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) via [`promise`](https://github.com/then/promise). * [`fetch()`](https://developer.mozilla.org/en/docs/Web/API/Fetch_API) via [`whatwg-fetch`](https://github.com/github/