You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using Flexi in my Ember js project for rendering templates under Layout folder based on device . The issue is Flexi works fine on MAC machine where we developed the application ,but when i moved the same code to Windows machine Flexi not working and it displays blank page without any errors in browser console. Any specific Flexi configration required for Windows machine ? Thanks in Advance
The text was updated successfully, but these errors were encountered:
Hi @AmeerGit, I think I saw this issue posted before either on GitHub or in Slack. Did you post something before? ember and ember-cli should work fine on any machine, although they have historically had some issues on Windows.
There is no specific Windows configuration or anything. It should work just fine. It probably depends heavily on what ember/ember-cli version you are on, how you are running it on Windows, if you are using command prompt or something that actually has bash, how you pull in node, and everything across the spectrum.
I don't have a Windows machine, but if you can give me a small reproduction of the issue, I could try to see if I see anything. Does the problem only happen running ember s or does it happen running builds as well?
@andreisebastianc-ccc do you have a more descriptive breakdown of the problem? It should work anywhere ember-cli works, as there is nothing unix specific that I know of.
I am using Flexi in my Ember js project for rendering templates under Layout folder based on device . The issue is Flexi works fine on MAC machine where we developed the application ,but when i moved the same code to Windows machine Flexi not working and it displays blank page without any errors in browser console. Any specific Flexi configration required for Windows machine ? Thanks in Advance
The text was updated successfully, but these errors were encountered: