Skip to content
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

Run blueprint manually #1052

Merged
merged 1 commit into from Jan 29, 2022
Merged

Run blueprint manually #1052

merged 1 commit into from Jan 29, 2022

Conversation

bendemboski
Copy link
Member

Unfortunately #1048 wasn't a full fix because electron-forge also has a dependency on chalk, so even without our own dependency, installing ember-electron could cause the hoisting to change triggering the underlying issue (ember-cli/ember-cli#7431).

So, until that issue in ember-cli can be addressed, we're no longer running the blueprint automatically. Instead, we point the default blueprint at a new one that simply prints out instructions telling the user to run ember g ember-electron manually.

Unfortunately #1048 wasn't a full fix because `electron-forge` also has a dependency on `chalk`, so even without our own dependency, installing `ember-electron` could cause the hoisting to change triggering the underlying issue (ember-cli/ember-cli#7431).

So, until that issue in `ember-cli` can be addressed, we're no longer running the blueprint automatically. Instead, we point the default blueprint at a new one that simply prints out instructions telling the user to run `ember g ember-electron` manually.
@bendemboski
Copy link
Member Author

@rwwagner90 I think this is our solution for now. I created a new branch off of this and cherry-picked your ember-cli 4.1 commits, and it passes. So my proposal is we do this for now, i.e. instruct users to run the blueprint manually, until ember-cli/ember-cli#7431 is addressed. Let me know what you think.

@RobbieTheWagner RobbieTheWagner merged commit 10ff66d into main Jan 29, 2022
@RobbieTheWagner RobbieTheWagner deleted the run-blueprint-manually branch January 29, 2022 00:14
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.

None yet

2 participants