-
Notifications
You must be signed in to change notification settings - Fork 215
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
[API] Warning: The .read and .rebuild APIs will stop working in the next Broccoli version #374
Comments
is |
@stefanpenner updated the description to aware/fixed. If it's deprecated and isn't going to be fixed, could we have a compat mode that uses https://github.com/broccolijs/broccoli-read-compat that people could enable perhaps? |
@oligriffiths how about this, if we see folks struggling with it. I'll take some time and make it compatible. (I'm guessing I'll need to do this anyways for work). Could I recommend we create a new section. |
Just wanted to add ember-cli/ember-cli-deprecation-workflow#52 to the list. It is the actual source of ember-template-lint/ember-cli-template-lint#345 according to ember-template-lint/ember-cli-template-lint#345 (comment) |
Hey it seems that For anyone having this issue, what helped me find out which addons cause this issue was to search in |
@oligriffiths Please give me a hint: How to start modifying TemplateCompiler, or what? I'm upgrading to ember-cli: 3.4.4 and is a bit confused in this for me rather new environment. I failed in an attempt to convert to yarn for a lot of reasons and had to fall back to bower for a probably 'bug dependency' reason, so it has been a long journey. These remaining errors/warnings should be removed since they may perhaps influence a few other unresolved code malfunctions that remain to work on. The package.json has got "broccoli": "^3.1.2", and "broccoli-plugin": "^2.1.0", Another WARNING that is always repeated is missing dependency 'fsevents' but I am not running MacOS but rather Kubuntu x64 (annoying verbose warnings, though). |
This error occurred in my Ember project after upgrading ember-cli from 3.4.3 to 3.18.0:
Please help. I cannot build the project or run ember serve while this exists |
I am having the same issue trying to upgrade ember-cli 3.4.3 to 3.18.0
|
What
This issue is to help inform Broccoli & Ember-CLI users when they experience this error/warning and to help with the transition.
Why
This warning is presented when broccoli is used with a plugin that is implementing the deprecated
.read/.rebuild
API.This API has been deprecated for some time, and will be removed very shortly when we switch to using Broccoli 2.0 in Ember-CLI.
The warning is generated here: https://github.com/ember-cli/broccoli-builder/blob/0-18-x/lib/builder.js#L241-L246
Unfortunately, due to the warning not being presented until build time, the instantiation stack of the plugin is lost, giving few details and limited introspect-ability to the source of the offender.
If you encounter this error after installing a new ember addon, please report the error to the addon author, and ask them to update their addon (or its dependencies).
If you encounter this error after updating ember-cli on an existing project, chances are you or an addon is using an old version of the broccoli-plugin API. Please post your error along with all the ember-addons you are using, and is possible a link to your project repository.
A temporary work around for plugin authors is to use https://github.com/broccolijs/broccoli-read-compat however we STRONGLY encourage you to update your plugin to the latest https://github.com/broccolijs/broccoli-plugin API
Thanks, we hope this journey is smooth.
Deprecated
These packages are deprecated and showing warnings, if there is demand we will put forward fixes:
ef4/ember-browserify
Fixed
Addons/plugins already aware/fixed:
ef4/ember-browserify#130
mainmatter/ember-simple-auth#1615
ember-template-lint/ember-cli-template-lint#345
ember-cli/ember-cli-deprecation-workflow#52
buschtoens/broccoli-flatiron#3
ef4/ember-code-snippet#52
embroider-build/ember-auto-import#52
The text was updated successfully, but these errors were encountered: