Similar to Laravel, I've added APP_NAME and NODE_ENV to the app.js config file.

Including APP_NAME, allows an easy way to have the name of an app consistent throughout the app, rather than having to hard code it in.

NODE_ENV removes the need to potentially use both Env and Config and condenses it down into just Config. A niche use case, but a use case none the less!

Any problems, or suggestions, I'm all ears!

Thanks again for the great framework! 💯

Version 10.0.0-beta.0 of standard just got published.

The version 10.0.0-beta.0 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of standard. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Your Greenkeeper Bot :palm_tree:

1- changed some security settings to make it more secure out-of-the-box 2- changed the data-upload limit for something more reasonable 3- added an env key for SESSION_DOMAIN for easier user exp 4- fixed some docs typos and made config files more consistent 5- added PATCH verb to csrf

Version 2.0.0 of youch just got published.

The version 2.0.0 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of youch. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Your Greenkeeper Bot :palm_tree:

Message is easier to read and understand instead of finding the message in the stack.

It'll be easier for newcomers to know what is the problem. The stack is also not really helpfull.

The current script name (dev & start) are too generic and can conflict if someone is using npm as a task launcher. Renaming them to serve & serve:dev is better in my opinion.

This change integrates Laravel Elixir into the base AdonisJS app. It supports everything Elixir does (except features requiring VueJS libraries, as these have been excluded from devDependencies). Versioning is also supported, by adding mix.version(...) to gulpfile.js, though I have disabled this by default as the generated files are uniquely named and would contaminate the build folder. An alternative to this exclusion would be to hook the gulp build task in to npm run start, so that the versioned assets are built before the elixir filter is executed, without needing the versioned assets to be committed to the repository.

I know you're not crazy about builders, because of the support expense. This seems like less of a problem since the filter is app-side, and Elixir is supported elsewhere. What do you think?

Edit: I don't know the best way to handle the unversioned check (inside the filter). Lacking brain, I have made the exists check synchronous/blocking. Perhaps you could suggest an alternate approach, assuming you're not 100% against this feature to begin with...

Not sure if this is where you want it, but I was surprised to see a default license and author and such when I created a new app. Also best practice to set private to true.