etcher/scripts/build/concatenate-javascript.sh
Juan Cruz Viotti 9c055fb165 fix(CLI): workaround absolute paths in Browserify bundles (#1409)
For some strange reason, Browserify will hardcode absolute paths from
the machine that generated the bundle to be able to resolve `__dirname`
and `__filename` calls. This makes no sense, given that it means that
the Browserify bundle will not work when we move it to another machine,
which went undetected probably for months.

The Browserify community apparently makes modules to fix this particular
issue (like `bundle-collapser`, and `intreq`), however none of this seem
to solve the problem for the Etcher CLI bundle.

I also gave https://github.com/zeit/pkg a go, however I gave up after
not being able to make use of native modules (nothing seems to work; the
packager result will simply not find the addons).

Finally, I ended up making the following workarounds:

- Edit the Browserify bundle file to use its own `__dirname` to
  dynamically resolve the values of `__dirname` and `__filename` of the
  files it contains

- Patch `lzma-native` to statically require its add-on rather than
  relying on dynamic requires from `node-pre-gyp`, which makes it
  impossible to resolve on the final bundle

See: https://github.com/resin-io/etcher/issues/355
See: http://stackoverflow.com/questions/21993073/browserify-with-paths-to-folders-in-my-system
Signed-off-by: Juan Cruz Viotti <jviotti@openmailbox.org>
2017-05-11 15:37:45 -04:00

87 lines
2.5 KiB
Bash
Executable File

#!/bin/bash
###
# Copyright 2016 resin.io
#
# 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.
###
set -u
set -e
BROWSERIFY="./node_modules/.bin/browserify"
./scripts/build/check-dependency.sh "$BROWSERIFY"
./scripts/build/check-dependency.sh uglifyjs
function usage() {
echo "Usage: $0"
echo ""
echo "Options"
echo ""
echo " -e <entry point (.js)>"
echo " -b <base directory>"
echo " -o <output>"
echo " -m minify"
exit 1
}
ARGV_ENTRY_POINT=""
ARGV_BASE_DIRECTORY=""
ARGV_OUTPUT=""
ARGV_MINIFY=false
while getopts ":e:b:o:m" option; do
case $option in
e) ARGV_ENTRY_POINT=$OPTARG ;;
b) ARGV_BASE_DIRECTORY=$OPTARG ;;
o) ARGV_OUTPUT=$OPTARG ;;
m) ARGV_MINIFY=true ;;
*) usage ;;
esac
done
if [ -z "$ARGV_ENTRY_POINT" ] ||
[ -z "$ARGV_BASE_DIRECTORY" ] ||
[ -z "$ARGV_OUTPUT" ]; then
usage
fi
"$BROWSERIFY" "$ARGV_BASE_DIRECTORY/$ARGV_ENTRY_POINT" --node --outfile "$ARGV_OUTPUT"
# This hack workarounds the fact the Browserify stores absolute paths
# of the machine that was used to produce the bundle, giving "not found"
# module errors when executing it in another computer.
# The fix is to replace absolute paths with `__dirname`
node <<EOF > "$ARGV_OUTPUT.TMP"
const separator = process.platform === 'win32' ? '\\\\\\\\\\\\\\\\' : '\\/';
const baseDirectory = process.platform === 'win32'
? "$ARGV_BASE_DIRECTORY".replace(/\//g, separator)
: "$ARGV_BASE_DIRECTORY";
const regex = new RegExp('"(.)+' + baseDirectory.replace(/\+/g, '\\\\+') + separator, 'g');
const contents = require('fs').readFileSync("$ARGV_OUTPUT", { encoding: 'utf8' });
console.log(contents.split('\n').map((line) => {
if (!regex.test(line)) return line;
return line
.replace(regex, 'require("path").join(__dirname,"')
.replace(new RegExp(separator, 'g'), '","') + ')';
}).join('\n'));
EOF
mv "$ARGV_OUTPUT.TMP" "$ARGV_OUTPUT"
if [ "$ARGV_MINIFY" == "true" ]; then
uglifyjs --compress --output "$ARGV_OUTPUT.MIN" -- "$ARGV_OUTPUT"
mv "$ARGV_OUTPUT.MIN" "$ARGV_OUTPUT"
fi