Use Bazel to build highlight.js
When including an already minified version of highlight.js,
it is difficult to add new versions or review changes.
So let's use Bazel to build our own highlight.min.js from node packages,
this way we can use yarn to manage the versions we include.
We include all standard HLJS languages plus soy, just as before.
When packaging Javascript with Rollup+Terser, we can even save
some bandwidth: the minified JS shrinks from ~1MB to ~875kB.
Change-Id: Ib972d5ce83b6da70a06e8dd60dca18a2b24a1a06
diff --git a/lib/highlightjs/rollup.config.js b/lib/highlightjs/rollup.config.js
new file mode 100644
index 0000000..c3a1340
--- /dev/null
+++ b/lib/highlightjs/rollup.config.js
@@ -0,0 +1,86 @@
+/**
+ * @license
+ * Copyright (C) 2021 The Android Open Source Project
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+const path = require('path');
+
+// In this file word "plugin" refers to rollup plugin, not Gerrit plugin.
+// By default, require(plugin_name) tries to find module plugin_name starting
+// from the folder where this file (rollup.config.js) is located
+// (see https://www.typescriptlang.org/docs/handbook/module-resolution.html#node
+// and https://nodejs.org/api/modules.html#modules_all_together).
+// So, rollup.config.js can't be in polygerrit-ui/app dir and it should be in
+// tools/node_tools directory (where all plugins are installed).
+// But rollup_bundle rule copy this .config.js file to another directory,
+// so require(plugin_name) can't find a plugin.
+// To fix it, requirePlugin tries:
+// 1. resolve module id using default behavior, i.e. it starts from __dirname
+// 2. if module not found - it tries to resolve module starting from rollupBin
+// location.
+// This workaround also gives us additional power - we can place .config.js
+// file anywhere in a source tree and add all plugins in the same package.json
+// file as rollup node module.
+function requirePlugin(id) {
+ const rollupBinDir = path.dirname(process.argv[1]);
+ const pluginPath = require.resolve(id, {paths: [__dirname, rollupBinDir] });
+ return require(pluginPath);
+}
+
+const cjs = requirePlugin('rollup-plugin-commonjs');
+const nodeResolve = requirePlugin('rollup-plugin-node-resolve');
+const {terser} = requirePlugin('rollup-plugin-terser');
+
+export default {
+ onwarn: warning => {
+ // No warnings from rollupjs are allowed.
+ // Most of the warnings are real error in our code (for example,
+ // if some import couldn't be resolved we can't continue, but rollup
+ // reports it as a warning)
+ throw new Error(warning.message);
+ },
+ output: {
+ format: 'iife',
+ compact: true,
+ strict: true,
+ exports: 'auto',
+ name: 'hljs',
+ footer: '',
+ plugins: [
+ terser({
+ output: {
+ comments: false
+ },
+ compress: {
+ ecma: 2015,
+ unsafe_arrows: true,
+ passes: 2,
+ unsafe: true,
+ warnings: true,
+ dead_code: true,
+ toplevel: "funcs"
+ }
+ })
+ ]
+ },
+ plugins: [
+ nodeResolve({
+ customResolveOptions: {
+ moduleDirectory: 'external/ui_npm/node_modules'
+ }
+ }),
+ cjs(),
+ ]
+};
