Open palpinter opened 8 years ago
Looks like a bug in the release candidate for 0.4.0. Use 0.3.13 in the meantime.
OK, thx.
Sorry, but result is same with 0.3.13
npm list -g | grep mantra-cli
├─┬ mantra-cli@0.3.13
Maybe caused by meteor 1.3.3?
The problem probably on my side. I've tried code generation on my other computer, and everything works as expected. I have to debug it.
Problem is with meteor 1.3.3. Absolute path no longer seem to work.
Changing the import in client/configs/context.js
from import * as Collections from '/lib/collections';
to import * as Collections from '../../lib/collections';
resolves the issue.
I do not know if this is a regression or intended.
Unfortunetely you should do it in all file where collections imported.
@palpinter Updating bebel-root-slash-import
will resolve the issue. See here. Can you check?
After fresh install I've received th following message:
Steps to reproduce:
mantra c testapp cd testapp meteor
from other console: mantra g collection testcoll
After remove 'undefined' from /lib/collections/index.js the result same.
Thx Pal