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
The co-assets-compiler used in production mode seems to require the asset directory to exist before starting up the server.
I get the following error when it doesn't exist:
$ NODE_ENV=production node .
connect.multipart() will be removed in connect 3.0
visit https://github.com/senchalabs/connect/wiki/Connect-3.0 for alternatives
connect.limit() will be removed in connect 3.0
AssetsCompiler Precompiling assets: coffee, styl
Hatch server listening on premium:3000 within production environment
uncaughtException
uncaughtException: ENOENT, readdir '/home/chrisf/dev/hatchjs/app/assets'
Notify error
uncaughtException: ENOENT, readdir '/home/chrisf/dev/hatchjs/app/assets'
The text was updated successfully, but these errors were encountered:
The co-assets-compiler used in production mode seems to require the asset directory to exist before starting up the server.
I get the following error when it doesn't exist:
$ NODE_ENV=production node .
connect.multipart() will be removed in connect 3.0
visit https://github.com/senchalabs/connect/wiki/Connect-3.0 for alternatives
connect.limit() will be removed in connect 3.0
AssetsCompiler Precompiling assets: coffee, styl
Hatch server listening on premium:3000 within production environment
uncaughtException
uncaughtException: ENOENT, readdir '/home/chrisf/dev/hatchjs/app/assets'
Notify error
uncaughtException: ENOENT, readdir '/home/chrisf/dev/hatchjs/app/assets'
The text was updated successfully, but these errors were encountered: