jmesserly@google.com
8982e4916f
Note: all of the changes to .debug.js and .min.js come from upstream I also simplified our patch, because we are now almost unforked upstream code (we just have a couple of fixes they haven't merged yet). In particular we can't use _ShadowDOMPolyfill$isGeneratedWrapper so we go back to 'GeneratedWrapper'. I'm trying to align our build logic more closely to: https://github.com/Polymer/platform/blob/master/gruntfile.js#L10, hence the use of their build.json files. This fixes: https://code.google.com/p/dart/issues/detail?id=13054 R=efortuna@google.com Review URL: https://codereview.chromium.org//23548014 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@27210 260f80e4-7a28-3924-810f-c04153c831b5
This folder contains the logic for building the shadow_dom package's concatenated and minified JS files.
Prerequisites
Install nodejs and npm. On Debian based systems this is typically:
sudo apt-get install nodejs
sudo apt-get install npm
- Install grunt-cli:
npm install -g grunt-cli
See the Grunt getting started page for more information.
Building
Run shadow_dom/tool/build.sh (from any directory):
./build.sh
(optional) How to integrate Polymer upstream changes
One time setup:
# Note: this requires commit access to dart-lang/ShadowDOM.
# You can use your own fork instead if you like.
# Just use that URL here and edit build.sh to pull from there.
git clone -b shadowdom_patches https://github.com/dart-lang/ShadowDOM.git
cd ShadowDOM
git remote add upstream https://github.com/Polymer/ShadowDOM.git
You can merge upstream changes by doing:
# Check that we are in shadowdom_patches branch and don't have
# any pending changes.
git status
git fetch upstream
git merge upstream/master
git push origin shadowdom_patches