Closed truedat101 closed 6 years ago
Hi @truedat101,
try to install latest version of Total.js $ npm install -g total.js
and let me know.
Unfortunately I'm stuck on a legacy version 1.7.2. I would need to port my app.
On Wed, Jul 11, 2018 at 1:43 PM Peter Širka notifications@github.com wrote:
Hi @truedat101 https://github.com/truedat101, try to install latest version of Total.js $ npm install -g total.js and let me know.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/totaljs/framework/issues/649#issuecomment-404303017, or mute the thread https://github.com/notifications/unsubscribe-auth/AAD6ylE1FUUhmlYmOvc-gQXMtiVBqR7nks5uFmNcgaJpZM4VLz6I .
Maybe I know where the problem is. Try to remove node_modules
from app diretory and perform translate
again and then recover node_modules
. Let me know.
So if I remove local node_modules in my app, in this case, just testing in totaljs-examples.git/views (pretty simple project), I get the same error.
Also, confirmed same error on Mac OS X with same versions.
I suspect if this was not working in the release I am testing, you have fixed this in a later release. If I know what was the problem I can patch locally as I have done in the past.
Try to install as a global module the latest version of Total: $ npm install total.js
and perform translate again. Your project will still use 1.7.2.
Hmm, that would work. I am curious what was wrong with 1.7.2. Anyway, I've gone ahead and migrated to total.js@1.9.8 with minimal code changes so I will sit fine with this slightly newer version for now.
Feel free to close if this is a "not going to fix" thing.
With total.js 1.7.2, running translate, regardless of web app I use, it will always fail with TypeError.