kopia lustrzana https://github.com/wagtail/wagtail
1da3e5fde7
- Accessing constructor was confusing and createController is not a core requirement - Avoid modifying the base Stimulus application class - Expose `window.StimulusModule` as the module output - Expose `window.wagtail.app` as the Wagtail Stimulus application instance - Rename root element variable to `root` in initStimulus (so we do not conflict with potential action option registration that uses `element` variable names) - Pull in the wagtail.components to the same core.js file and add JSDoc for exposed global - Relates to #10197 |
||
|---|---|---|
| .. | ||
| scss | ||
| src | ||
| storybook | ||
| tests | ||
| README.md | ||
| extract-translatable-strings.js | ||
| package-lock.json | ||
| tailwind.config.js | ||
| webpack.config.js | ||
README.md
Wagtail client-side components
This library aims to give developers the ability to subclass and configure Wagtail's UI components.
Usage
npm install wagtail
import { Explorer } from 'wagtail';
// [...]
<Explorer />;
Development
# From the project root, start the webpack + styles compilation.
npm run start
You will also need:
- React DevTools – React developer tools integrated into Chrome.
- Redux DevTools – Redux developer tools integrated into Chrome.
Releases
The front-end is bundled at the same time as the Wagtail project. This package also aims to be available separately on npm as wagtail.