Skip to content

Commit

Permalink
Ensure build-metadata.json is included in packed tarball.
Browse files Browse the repository at this point in the history
(cherry picked from commit 2e9d90a)
  • Loading branch information
rwjblue committed Jan 12, 2018
1 parent c2b7d49 commit 1f05c15
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 4 deletions.
8 changes: 4 additions & 4 deletions bin/build-for-publishing.js
Expand Up @@ -47,10 +47,6 @@ execSync('yarn build');
execSync('yarn docs');
updateDocumentationVersion();

// using npm pack here because `yarn pack` does not honor the `package.json`'s `files`
// property properly, and therefore the tarball generated is quite large (~7MB).
execSync('npm pack');

// generate build-metadata.json
const metadata = {
version: VERSION,
Expand All @@ -59,3 +55,7 @@ const metadata = {
assetPath: `/${process.env.BUILD_TYPE}/shas/${process.env.TRAVIS_COMMIT}.tgz`,
};
fs.writeFileSync('build-metadata.json', JSON.stringify(metadata, null, 2), { encoding: 'utf-8' });

// using npm pack here because `yarn pack` does not honor the `package.json`'s `files`
// property properly, and therefore the tarball generated is quite large (~7MB).
execSync('npm pack');
1 change: 1 addition & 0 deletions package.json
Expand Up @@ -11,6 +11,7 @@
},
"license": "MIT",
"files": [
"build-metadata.json",
"blueprints",
"dist",
"!dist/ember-tests.prod.js",
Expand Down

0 comments on commit 1f05c15

Please sign in to comment.