mirror of
https://github.com/streetwriters/notesnook.git
synced 2025-12-16 19:57:52 +01:00
c0a99427d9
* test: intialize testing environment * test: add an example test for reference * test: add simple navigation test * some initial tests * some changes * name and other small changes * permanently delete a note * permanenlt delete a note * test: improve test readability I have added different id builders for building test ids. They make the tests more readable and fluent. * test lock a note * test add a note to notebook * test favorite a note * test pin a note * test: further improve test readability basically I refactored some frequently performed actions into helper functions * test: check for presence of toast * test: properly test pinned note * test: increase tests reliability * test: fix all tests * perf: load 2co script & fonts when needed * ci: initialize e2e gh test runner * ci: do not run npm ci * test: fix lock note test for all browsers * ci: fix playwright tests * ci: fix yaml syntax error * ci: no need to use custom ssh-agent action for eslint * test: improve lock a note test * ci: add GH_DEPLOY_KEY env in eslint.yml * test: check for state: "visible" in isPresent * test: do not check for toast in lock a note test * test: log crypto error to console * test: skip "lock a note" test for now until further investigation * ci: only run tests on firefox & chromium * fix: fix useMediaQuery for WebKit browsers * ci: try webkit once again * properties tests * test tag a color /properties * test: run some tests sequentially and independently * test: reenable all tests * fix: user only able to type on character in title box * test: skip lock/unlock tests in CI * test edit a notebook * test: fix all tests * test: fix and add more notebook tests * test: do not only run edit topics test * test: make sure all notes tests pass * test: skip add note to notebook tests for now * test: make sure all tests pass Co-authored-by: alihamuh <alihamuh@gmail.com>
38 lines
1.3 KiB
JavaScript
38 lines
1.3 KiB
JavaScript
process.env.NODE_ENV = "production";
|
|
|
|
const webpack = require("webpack");
|
|
const BundleAnalyzerPlugin = require("webpack-bundle-analyzer")
|
|
.BundleAnalyzerPlugin;
|
|
const webpackConfigProd = require("react-scripts/config/webpack.config")(
|
|
"production"
|
|
);
|
|
|
|
// this one is optional, just for better feedback on build
|
|
const chalk = require("chalk");
|
|
const ProgressBarPlugin = require("progress-bar-webpack-plugin");
|
|
const green = (text) => {
|
|
return chalk.green.bold(text);
|
|
};
|
|
|
|
// pushing BundleAnalyzerPlugin to plugins array
|
|
webpackConfigProd.plugins.push(new BundleAnalyzerPlugin());
|
|
|
|
// optional - pushing progress-bar plugin for better feedback;
|
|
// it can and will work without progress-bar,
|
|
// but during build time you will not see any messages for 10-60 seconds (depends on the size of the project)
|
|
// and decide that compilation is kind of hang up on you; progress bar shows nice progression of webpack compilation
|
|
webpackConfigProd.plugins.push(
|
|
new ProgressBarPlugin({
|
|
format: `${green("analyzing...")} ${green("[:bar]")}${green(
|
|
"[:percent]"
|
|
)}${green("[:elapsed seconds]")} - :msg`,
|
|
})
|
|
);
|
|
|
|
// actually running compilation and waiting for plugin to start explorer
|
|
webpack(webpackConfigProd, (err, stats) => {
|
|
if (err || stats.hasErrors()) {
|
|
console.error(err);
|
|
}
|
|
});
|