Ember CLI ember new and ember init files not showing but buildable

Question

I'm using ember v1.13.15, node: 5.4.1, npm 2.14.10 and os linux x64 (ubuntu). I'm actually trying to get ember-cli into my rails app. When executing ember new frontend I get the output that a bunch of files were created. These files don't show up in nautilus, terminal via ls nor can I cd into the directory. I manually typed mkdir frontend && cd frontend then ember init with the same results. If I run ember init again it recognizes the files are there because it asks me if I want to overwrite some files.

Running ember build produces a successful build, but where are the files?

Updated with terminal

uhoh@eblinux:~/Documents/apps/mvp$ cd frontendconsumer/
uhoh@eblinux:~/Documents/apps/mvp/frontendconsumer$ ls
uhoh@eblinux:~/Documents/apps/mvp/frontendconsumer$ ember init
version: 1.13.15
Could not find watchman, falling back to NodeWatcher for file system events.
Visit http://www.ember-cli.com/user-guide/#watchman for more info.
installing app
  identical .bowerrc
  identical .editorconfig
  identical .ember-cli
  identical .jshintrc
  identical .travis.yml
  identical .watchmanconfig
  identical README.md
  identical app/app.js
  identical app/index.html
  identical app/router.js
  identical app/templates/application.hbs
  identical bower.json
  identical config/environment.js
  identical ember-cli-build.js
  identical .gitignore
  identical package.json
  identical public/crossdomain.xml
  identical public/robots.txt
  identical testem.json
  identical tests/.jshintrc
  identical tests/helpers/destroy-app.js
  identical tests/helpers/module-for-acceptance.js
  identical tests/helpers/resolver.js
  identical tests/helpers/start-app.js
  identical tests/index.html
  identical tests/test-helper.js
Installed packages for tooling via npm.
Installed browser packages via Bower.
uhoh@eblinux:~/Documents/apps/mvp/frontendconsumer$ ls
uhoh@eblinux:~/Documents/apps/mvp/frontendconsumer$ ls -a
. ..

Update v2

    uhoh@eblinux:~/Documents/apps/mvp/frontendconsumer$ locate test-helper.js --all
    /home/uhoh/Documents/apps/integration/node_modules/jshint/node_modules/htmlparser2/test/test-helper.js
    /home/uhoh/Documents/apps/newapp/node_modules/jshint/node_modules/htmlparser2/test/test-helper.js
    /home/uhoh/Documents/apps/vd-integrations/test/test-helper.js
    /home/uhoh/Downloads/ace1.3.1/mustache/js/node_modules/htmlparser2/tests/test-helper.js
    /home/uhoh/Downloads/ace1_3.0/mustache/js/node_modules/htmlparser2/tests/test-helper.js
/home/uhoh/Downloads/ace3/mustache/js/node_modules/htmlparser2/tests/test-helper.js
/home/uhoh/consumer_frontend/node_modules/ember-cli/blueprints/app/files/tests/test-helper.js
/home/uhoh/consumer_frontend/node_modules/ember-cli-babel/tests/test-helper.js
/home/uhoh/consumer_frontend/node_modules/ember-cli-content-security-policy/tests/test-helper.js
/home/uhoh/consumer_frontend/node_modules/ember-cli-qunit/node_modules/broccoli-jshint/node_modules/jshint/node_modules/htmlparser2/test/test-helper.js

Answer 1

I am unable to comment, so instead I will offer you two main options:

• Uninstall all ember related packages and push node to 5.6.0 and npm to 3.6.0 (the version that I using.)

  1. npm uninstall -g ember-cli
  2. sudo npm cache clean -f
  3. sudo npm install -g n
  4. sudo n stable
  5. Install Ember and the needed packages, confirm version of node and npm and try to create the project.

• Probe the files on the frontendconsumer folder:

  1. Typesyncand see if something shows up on Nautilus.
  2. Use locate test-helper.js -c or locate any other file that was supposed to be there. If the result is 0 then give the other locate params a try.
  3. Type baobab and see if something shows up on the folder.
  4. If nothing yet, then try find -type l to see if there are any symbolic links.
  5. Run a checkdisk on your hard drive.

If none of those options helped, then something really weird is going when scaffolding the new application... If there is no other issues on your system, try to create a rails app through RVM to see if the scaffold of a new app works out. If it does, then chances are that something within npm, node or the ember packages are bad. Otherwise, it may be your system.