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

Normalize to always import from 'backburner.js' #20328

Closed
wants to merge 1 commit into from

Conversation

chriskrycho
Copy link
Contributor

We had a mix of different import locations for this, both the ES imports via backburner.js and the Ember CLI-munged version available at backburner. Switch to only using the Node-resolveable version, so TS can resolve it correctly; and enforce it by removing backburner from the list of core modules in the ESLint config.

@chriskrycho chriskrycho marked this pull request as draft December 22, 2022 15:14
We had a mix of different import locations for this, both the ES
imports via `backburner.js` and the Ember CLI-munged version available
at `backburner`. Switch to only using the Node-resolveable version, so
TS can resolve it correctly; and enforce it by removing `backburner`
from the list of `core` modules in the ESLint config.
@chriskrycho
Copy link
Contributor Author

This is blocked on figuring out what part of the build pipeline makes backburner.js only importable as backburner.

@chriskrycho
Copy link
Contributor Author

Fixed along the way to #20449, and I just forgot to close it!

@chriskrycho chriskrycho closed this Oct 5, 2023
@chriskrycho chriskrycho deleted the backburner-import branch October 5, 2023 23:04
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.

1 participant