-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Embroider build replaces Fastboot generated package.json #160
Comments
Moving to I think we should deal with this in embroider. Probably by detecting the package.json in the public tree and merging it into our own. |
After adding the above fix in the test app I noticed following issues with Embroider+Fastboot build:
Investigating ^ issues. Will update here. |
This was closed by #178. |
Reopened because the fix was reverted. |
Should be fixed by #383 if I didn't missed something. |
Although the PR mentioned above seems to address the issue, I am still running into it, with the latest embroider release (0.27.0). You can see that quite well when building the In an embroider build ( package.json
In a classic build ( package.json
The error that I see is not the one mentioned in the original comment, but rather Will provide a PR with a failing test... |
Adds accessing `request.host` to `fastboot-app` that reproduces the missing FastBoot package.json data (here `hostWhitelist`) reported in embroider-build#160.
Here is a failing test: #574 |
I don't think your problem is related to this issue. In your package.json, you can see that we did emit fastboot info, it's just that it's using |
You are right, I didn't pay enough attention to the FastBoot manifest data it seems. It was just obvious that it was totally different, so I wrongly assumed Embroider had omitted something. Until I realized that Embroider has some custom adapter for ember-cli-fastboot, which seems to explain the vast difference between builds. I think I have found a fix, will update my PR, then let's move the discussion over there... So, as my issue is indeed not really related to this issue, which seems to have been fixed by now, I think we can close this... |
My PR - ember-fastboot/ember-cli-fastboot#690 moved the implementation form the postProcessTree to treeForPublic hook. But after doing that, I noticed embroider build doesn't add the package.json generated by
ember-cli-fastboot
addon. Instead, it keeps the package.json created by enbroider build in the dist folder. I am thinking some diff code is assuming the package.json generated as part of Fastboot tree is similar to package.json generated by embroider build and keeps embroider build related package.jsonTo Repro the issue
yarn install
page will show following error:
This error is thrown because
manifest
property is missing in generated package.json.I am thinking the fastboot generation of package.json should move to
postBuild
hook instead of usingtreeForPublic
. what do you guys think @ef4 @stefanpenner @rwjblueRelated to issue - #112
I missed this error during testing of my PR as the git repo mentioned in the above issue didn't include fastboot and I tested assuming ember-cli-fastboot was included as dependency. :(
The text was updated successfully, but these errors were encountered: