-
Notifications
You must be signed in to change notification settings - Fork 159
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
htmlSafe function not available in @ember/string but only in fastboot #855
Comments
@mansona did you ever figure this out? I'm seeing same thing after updating deps |
I have experienced something similar, however in my case it was merely triggering a deprecation. And I was only seeing it in the browser, but not on the fastboot server. While trying to find a solution, someone suggested this issue: emberjs/ember-string#235 (comment) essentially there are competing implementations in ember-source and possibly this issue will also fix that emberjs/ember.js#20383 |
v5.0 of ember-source removes the internal implementation of v3.0.1 of |
Yes I think this can be closed too 👍 |
When running in fastboot we get an error
TypeError: (0 , _string.htmlSafe) is not a function
but running the same app in the browser doesn't have the same issue.I have noticed this issue with the Ember Blog https://github.com/ember-learn/ember-blog and when debugging I can confirm that the object that is injected in place of
@ember/string
does indeed not have thehtmlSafe
function.In Fastboot:
The exact same code in the browser:
Something else that is odd with this error is that it is a "caught error". For me to hit it in the debugger I had to select "Pause on caught exceptions". It also doesn't register as an error when doing a Prember run which means that we have not been Fasbooting the Ember blog for a while now and we just didn't notice 🙈
I know this is a known deprecation and with Ember 4.0 it is pretty urgent to fix as quickly as possible but I'm surprised that this is broken in fastboot and working in the browser 🤔
The text was updated successfully, but these errors were encountered: