wagtail/client
Thibaud Colas ee15eec511 Switch all Node tooling from Gulp to Webpack, with needed code changes
- Remove gulp code and docs
- Add base CSS & SCSS processing in Webpack
- Make sure Sass files use paths that can be resolved by Webpack
- Use faster source map generation
- Clean up build scripts
- Make sure Storybook can process Sass
- Switch away from web fonts (more work needed)
2022-02-01 07:36:17 +10:00
..
.storybook Switch all Node tooling from Gulp to Webpack, with needed code changes 2022-02-01 07:36:17 +10:00
scss Switch all Node tooling from Gulp to Webpack, with needed code changes 2022-02-01 07:36:17 +10:00
src Switch all Node tooling from Gulp to Webpack, with needed code changes 2022-02-01 07:36:17 +10:00
tests Upgrade ESLint configuration, with needed refactorings 2022-02-01 07:36:17 +10:00
README.md Refactor explorer code with tests using Jest 2017-05-13 23:53:10 +03:00
package-lock.json Feature/field comment frontend (#6530) 2021-04-20 18:25:30 +01:00
webpack.config.js Switch all Node tooling from Gulp to Webpack, with needed code changes 2022-02-01 07:36:17 +10:00

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:

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.