Skip to content

Fix push manifest generation bugs affecting bower_components and ES modules#512

Merged
usergenic merged 6 commits intomasterfrom
push-manifest-bugs
Jun 16, 2018
Merged

Fix push manifest generation bugs affecting bower_components and ES modules#512
usergenic merged 6 commits intomasterfrom
push-manifest-bugs

Conversation

@aomarks
Copy link
Member

@aomarks aomarks commented Jun 13, 2018

This PR fixes two issues with push manifest generation:

  1. Projects with bower_components were getting paths relative to the package root instead of the project root. This seems to have been a regression in 1.7 (addPushManifest treats app dependencies as siblings #433).

  2. Projects with ES modules were crashing on push manifest generation because it was unable to resolve bundler's special sub-bundle URLs (e.g. Unable to get document file:///private/var/folders/wz/fv09mcr569gdkbzqct263l_r003hs9/T/tmp-84970LqLvdcKS3nbH/index.html>external#1>mod1.js>es6-module: unknown).

@aomarks aomarks requested a review from usergenic June 13, 2018 07:36
@usergenic
Copy link
Contributor

Need to fix; test:unit failing reliably due to change.

aomarks added 2 commits June 13, 2018 14:47
Previously it looks like we were implicitly relying on the current
working directory?

This also means we don't have to manually fix up relative URLs in push
manifest generation, so reverted that.
@aomarks
Copy link
Member Author

aomarks commented Jun 13, 2018

Need to fix; test:unit failing reliably due to change.

Fixed. PTAL.

Copy link
Contributor

@usergenic usergenic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants