esbuild-sass-plugin 2.10 got released as compatible with 2.8, but it is
not compatible any more with esbuild 0.17.18. Bump both.
(cherry picked from commit d3b9064d63)
... and make use of the new pywrap feature from our test.
Use the same eslint and stylelint plugin configuration as the cockpit
main repo.
Co-authored-by: Katerina Koukiou <kkoukiou@redhat.com>
(cherry picked from commit 2215aa3bf8)
Bump Cockpit commit to pick up the necessary adjustments for latest PF,
and adjust test for the new "-v5" namespace prefix.
Closes#654
(cherry picked from commit 092cefab3b)
These are already installed as dependencies, and we do the same in other
Cockpit projects. The latest react-styles version became incompatible
with the react-core version, causing a build failure.
(cherry picked from commit a47c641af9)
Fixes these `npm install` warnings:
> deprecated babel-eslint@10.1.0: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
> deprecated eslint-loader@4.0.2: This loader has been deprecated. Please use eslint-webpack-plugin
Cherry-picked from starter-kit commit 0e608d562a
node-sass is a compiled ELF module, which is problematic for
distributions that want to rebuild everything from source. The sassc CLI
program is packaged everywhere, and both use the same libsass library.
So drop node-sass and replace it with sass which is also what cockpit
and other external plugins are using.
Port alerts in PF-react-core and fix missing icons in alerts
This addresses an issue with typeahead search generating a significant
load on the system, a single filter test run can make ~100 calls to
journalctl restart if not throttled.
Taken rules from Cockpit, which have been proven to be effective for
finding bugs and keeping clean code, and sensible (not taking
unreasonable effort to satisfy).
Fix code layout in app.jsx accordingly.
Closes#39
eslint is much more powerful and flexible than jshint, and we don't want
to promote writing new projects with pre-ES6 code.
As a side effect, this also avoids downloading PhantomJS (see
https://github.com/jshint/jshint/issues/3318), thereby cutting down
node_modules/ from 470 MB to 210 MB.
This makes sure we always include all files in the repository when
disting.
Obsoletes webpack-with-stats, which had a bug anyway: it wasn't
reporting jslint errors.
This moves us one step closer to a normal source package. The sources
are now unpacked and we run "make install". We still don't build
since we don't have all the necessary tools.
Also, most importantly, the source tarball now includes our actual
sources in addition to the prebuilt binaries.
