Scaffold an official project structure
Add --bare option to meteor create
Notice scaffold options on meteor create
add full skeleton
add spaces
remove shell-server package from skew-full + add description of new packages
Add --bare option to meteor create
Notice scaffold options on meteor create
add full skeleton
add spaces
remove shell-server package from skew-full + add description of new packages
improve PR
resolve conflict
Fix rebase
fix static-assets readme
Fix tipo
Remove insecure and auto publish packages
Remove useraccounts-configuration.js
add tests
fix PR
Note there are a few use cases I can think of we want to worry about:
`meteor run` -- both should be "development"
`meteor run --production` - both should be "production"
`NODE_ENV=production meteor run` - as above
`NODE_ENV=development meteor run --production` - `--production` should win
`meteor test` - NODE_ENV should be "development", buildMode should be "test"
`NODE_ENV=production meteor test" - NODE_ENV should be "production", buildMode should be "test"
Our old "unit" test mode didn't really enforce "unit-ness" and was perfectly capable of running integration test. So it was confusing to call the two modes unit and integration test modes.
Instead, we call them "test mode" and "full app test mode", run with `meteor test` and `meteor test --full-app`.
The rules for test files were also simplified -- simply *.test[s].* for test mode, and *.app-test[s].* for full app tests. `tests/` directories are simply ignored again.
