-
Notifications
You must be signed in to change notification settings - Fork 99
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
(un)feat: remove MU support from the default blueprint #826
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
], | ||
"in-repo-b/*": [ | ||
"tests/dummy/lib/in-repo-b/addon/*" | ||
] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙏
describe('module unification', function() { | ||
it('generates .d.ts files from the src tree', async () => { | ||
describe('custom project layout', function() { | ||
it('generates .d.ts files from the specified source tree', async () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
- Removes support in the default blueprint for initializing new Module Unification projects, in line with [MU's removal][MU] from Ember's roadmap in favor of other directions. Existing MU projects should continue to build and typecheck according to the local `tsconfig.json`. ([#826](https://github.com/typed-ember/ember-cli-typescript/pull/826)) | ||
|
||
[MU]: https://blog.emberjs.com/2019/03/11/update-on-module-unification-and-octane.html | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
lol, I'm always asking for changelog in PRs at work, but didn't think to require that here 😉
This PR implements the portion of #806 corresponding to
ember-cli-typescript
itself — the remainder of the change will be in the blueprints package.We still support building/typechecking/generating
.d.ts
files for nonstandard project layouts, but the default blueprint will no longer support configuring new MU projects for TypeScript automatically.