-
Notifications
You must be signed in to change notification settings - Fork 33
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
Prevent inconsistent ember-cli builds with different extensions #166
Comments
I haven't had a chance to look at this yet, but seems important. If you have free time to provide a failing test, that would very much help me. |
@stefanpenner I'm not sure the best way to write a thorough test for this, since the issue is nondeterminism. As far as I know this same issue applies to the core If I write a plugin like this: class MyPlugin extends PersistentFilter {
constructor(input) {
super(input, {
extensions: ['foo', 'bar'],
targetExtension: 'txt'
});
}
processString(content, relativePath) {
// Just write the extension of the input file as its content
return path.extname(relativePath);
}
} And then run that over a directory that has both Concretely the way folks are running into this is with addons' One way to solve this would be to have the order that |
This might be the underlying reason for emberjs/data#6697 We changed the file from a |
This issue hits us really hard on all our TypeScript projects. We can work around it with our own addons, but there's nothing we can do with third-party addons, other than forking them. 😕 Due to this issue, Is anyone working on this? |
No, not to my knowledge |
We've worked around this in ember-cli-typescript using broccoli-stew's |
Still an issue today. Does Embroider v2 package format remove this problem? |
Maybe this is correct place for this issues collection, if not, feel free to close it or redirect me to proper repo.
ember-cli/ember-ajax#428
typed-ember/ember-cli-typescript#724
emberjs/ember-cli-babel#240
The text was updated successfully, but these errors were encountered: