-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
Use content-tag, which fixes *all the bugs* #187
Use content-tag, which fixes *all the bugs* #187
Conversation
1499bb7
to
91869d7
Compare
Failures exist over here: #190, so it has nothing to do with content-tag |
What does this mean?
|
0b4be0e
to
4382efc
Compare
eslint-plugin-ember and ember-template-lint will need to remove their (peer)dependencies on ember-template-imports, because the prettier-plugin-ember-template-tag should be fine because it declares its own hard dependency on There are paths forward for each of these, and @patricklx has been doing awesome work making legit lint tooling and I don't know what or if there is a story for combining efforts with content-tag, but the benefits, impact, and desire for getting the tools off of ember-template-imports is described here: #143 |
b2d0d8b
to
0473a0f
Compare
There's a bit of bitrot, so I'm going to open some other PRs to try to make this easier.
My hope is that I can avoid waiting for typed-ember/ember-cli-typescript#1569 as well, but timing might work out where it's no big deal. |
d253a01
to
9b0a835
Compare
c51cc12
to
414e545
Compare
Running in to:
I remember ember-compatibility-helpers having issues throughout the years. The modern way do to what it wants to do is embroider/macros. |
update: by switching to pnpm,
old comment: We need to merge / release:
Gonna switch this project to pnpm in another PR tho, because yarn can't handle the state of our dependencies right now (locally, I have tests passing, but in yarn, I have the above ember-compatibility-helpers issue, which is typically due to incorrect duplicate dependencies in the dep graph) |
cbc7ac0
to
ecedffe
Compare
521b32a
to
419cea4
Compare
- ember-cli-babel 8.1+ - required `@babel/core` (declared as peer) - ember-cli-htmlbars 6.3.0+ - allowed us to remove babel plugins from our dependencies - content-tag 1.1.1+ and allows for: - removal of all hbs-supporting code - removal of now-extraneous testing - removal of custom processor - removal of custom preprocessor plugin management To get CI passing, - ie11 support had to be removed in targets.js (latest ember does not support ie11) - `@embroider/test-support` and `ember-try` had to be upgraded so they pull in supported dependencies today
…in-helpers (not used)
776ef29
to
a3091f9
Compare
It says it fixes all the bugs. But didn't close any GitHub issues :) |
Oops. Thanks! |
Learned some new cli-fu today:
the actual diff!
Breaking changes
all consumers that were importing from ember-template-imports will no longer be able to.
folks should typically want to use
content-tag
instead ofember-template-imports
after this change.BlockersExtra bonus -- most of the code from the original implementation is gone now 🎉 yay deleting code!
(most of the additions are lockfile, btw)
((also most of the removals, but also 98% of the old code is gone, too))
This is a breaking change, however:
hbs
supportRelated,
tsc
is no longer needed, so I removed that from the package.json scriptsbuild
andjest
Not related,
node/no-missing-require
-- because it's buggy. and eslint-plugin-node hasn't been maintained for quite some time -- long term solution here is to switch to esilnt-plugin-nnode/no-unpublished-require
-- because it doesn't understand how peer dependencies work.resolved issues encountered while working on this PR
What I need help with,
why did I need to add@babel/plugin-transform-class-static-block
? browsers support this (I got a babel error about needing to add this)UPDATE: I have things working on stackblitz -- so I don't yet know what's going on with C.I.:
Supersedes #182