:evergreen_tree: Modern Web Application Framework for Node.js.

Issue Description

yo trails not generating default folders controllers & models in api folder. Due to this config/web.js also not generating itself.

Some trailpacks's not been installed, Error is as below

npm ERR! Linux 4.8.0-32-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "trailpack-express@v2-latest" "trailpack-mongoose@v2-latest" "trailpack-footprints@v2-latest" "[email protected]" "--save" "--silent" "--loglevel=error"
npm ERR! node v6.0.9
npm ERR! npm  v4.1.1
npm ERR! code ETARGET
npm ERR! notarget No compatible version found: trailpack-mongoose@v2-latest
npm ERR! notarget Valid install targets:
npm ERR! notarget 0.1.0, 0.2.0, 0.2.2, 0.3.0, 0.4.0, 0.4.1, 0.4.2, 0.4.3, 0.4.4, 1.0.0, 1.0.1
npm ERR! notarget 
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/nd/Desktop/ND/trails-hello/npm-debug.log
1
┌───────────────────────────────────────────┐
│ Your Trails Application has been created! │
│ ---                                       │
│ To start your application, run: npm start │

Environment

• node version: 6.0
• trails version: 2
• operating system: Ubuntu16.10 & Mac Sierra

In order to make all Trailpacks compatible whatever the web server choice, we need a unified API for controllers and policies.

module.exports = class MyController extends Controller{
  /**
    * params : url parameters
    * query : get parameters
    * body : payload
  **/
  info(params, query, body, next){
    next(null, {status: 200, data: {whatever:'ok’}, headers:[]})
  } 
}

But actually controllers/policies are bind directly to web server so I don't see how we can implement this :/. Any idea ?

Issue Description

Unable to generate a Trails project with Yo. I just install yo and generator-trails. Then, I execute this command yo trails. I enter my options and nothing happens after the module name option.

Environment

• node version: v6.1.0
• trails version: ???
• operating system: Windows 10 64bits

Issue Description

I apologize if this is not the write way to report this.

Watching what I think is a video by you guys (https://www.youtube.com/watch?v=AbSp8jqFDAY) I am not able to get a response from the GET request to /api/v1/user:

# curl http://localhost:3000/api/v1/user

{
  "statusCode": 404,
  "error": "Not Found"
}

To recreate this, I created a new project, installed the latest generator-waterline (alpha-6, prior versions don't seem to work anymore), and added require('trailpack-waterline') to main.js.

The tutorial seems to autogenerate routes for the builtin User model. Am I missing something?

Environment

• node version: 5.10.1
• trails version: 1.0.0-beta-1
• operating system: Linux 4.2.0-34-generic #39-Ubuntu x86_64 x86_64 x86_64 GNU/Linux

Edit: Here are the packages I have (noticed I put the wrong version for trails):

"dependencies": {
    "lodash": "^4.0",
    "trailpack-core": "^1.0.0-beta-3",
    "trailpack-hapi": "^1.0.0-beta-3",
    "trailpack-repl": "^1.0.0-beta-3",
    "trailpack-router": "^1.0.0-beta-4",
    "trails": "^1.0.0-beta-1",
    "trails-controller": "^1.0.0-beta-2",
    "trails-model": "^1.0.0-beta-2",
    "trails-policy": "^1.0.1",
    "trails-service": "1.0.0-beta-2",
    "waterline-sqlite3": "^1.0.0",
    "winston": "^2.1.1"
  },

It would be nice to have some classes : TrailsModel, TrailsController, TrailsPolicy and TrailsService instead of {} directly. It can be useful to extends some trailpack functionalities from trails project. It can be more 'cleaner' / easy to understand/learn to have classes for this kind of objects.

Issue Description

Actually it's not possible to write Trails files (api/config) with TypeScript or CoffeeScript format. A trailpack can't do it because when Trails start nothing was load (because they are no JS files, only .ts or .coffee).

In order to fix this we can create trails-compiler module witch need to be override by trails-compiler-typescript and trails-compiler-coffee ...

The Trails app is launch by node server.js so the first thing to do in server.js is to check if there a trails-compiler, if one (or more ?) is present server.js launch them to compile every sources into JS. Once compiled server.js can do like now and start the Trails app :)

Some interface need to be think/create for trails-compiler in order to work correctly but like this Trails can be compatible with any JS derivate languages (even Dart if some are courageous lol).

For instance each trails-compiler will embed an archetype of Trails project (but in ts, coffee...) that can be use in the generator to generator a Trails project in ts, coffee...

That's a start and it's an open discussion here ^^

Description

Config between app/trailpack is merge in the wrong way.

No fix yet, just create the right unit test of what we really want. Waiting for @tjwebb feedback on #316 issue

Issues

• resolves #316

info: Starting...
debug: trails event: trails:start
verbose: Trailpacks: All Validated.
debug: trails event: trailpack:all:validated
debug: trails event: trailpack:core:configured
debug: trails event: trailpack:repl:configured
debug: trails event: trailpack:router:configured
debug: trails event: trailpack:hapi:configured
debug: trails event: trailpack:all:configured
debug: trails event: trailpack:core:initialized
debug: trails event: trailpack:repl:initialized
debug: trails event: trailpack:router:initialized
error:
 AssertionError: missing path
    at Module.require (module.js:364:3)
    at require (module.js:385:17)
    at Object.registerViews (/Volumes/Repos/Coding/OpenSource/trails/test/node_modules/trailpack-hapi/lib/server.js:28:15)
    at Hapi.initialize (/Volumes/Repos/Coding/OpenSource/trails/test/node_modules/trailpack-hapi/index.js:37:16)
    at /Volumes/Repos/Coding/OpenSource/trails/test/node_modules/trails/index.js:65:26
    at process._tickDomainCallback (node.js:422:9)
    at Function.Module.runMain (module.js:459:11)
    at startup (node.js:138:18)
    at node.js:974:3
debug: trails event: trails:stop

Issue Description

Every time need to install colors after using yo tails

C:\Users\Scw\Desktop\tra>node server.js
module.js:327
    throw err;
    ^

Error: Cannot find module 'colors'
    at Function.Module._resolveFilename (module.js:325:15)
    at Function.Module._load (module.js:276:25)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous>  (C:\Users\Scw\Desktop\tra\node_modules\trailpackrepl\node_modules\big-tree-cli\index.js:1:76)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)

Environment

• node version: v4.4.4
• trails version: ^1.0.0-beta-1
• operating system: Window 7

Issue Description

As I see under all trailpacks, to remove multiple items you need to call url like DELETE http://localhost:3000/api/v1/mymodel?name=test

This will remove all items with name = test with works fine. But if you try something like : DELETE http://localhost:3000/api/v1/mymodel?isOk=true DELETE http://localhost:3000/api/v1/mymodel?nbTodo=4

None of this url will work because when params are parse they are all in string so on Footprint Controller and FootprintService we have isOk = "true" and nbTodo="4" and the ORM will crash or worse execute the query successfully but 0 items was deleted.

Environment

• node version: all
• trails version: all
• operating system: all

Some of the wording in the answer to 'Is Trails a fork of Sails?' is a little misleading, so would be a good idea to change it to avoid confusion about this project. Right now it says:

Trails is built and maintained by former members of the Sails.js core team

But that makes it sound like the core maintainers of Sails have become involved in this project. It would be more accurate to change it to something along the lines of:

Trails is built and maintained by a former Sails contributor and his team

(Would have submitted a PR myself, but I figured you might want to work with the wording a bit more before changing it.)

Hello,

I'm using Trails for the first time, when I type npm start in the terminal I have no answer.

@ 0.0.0 start /var/projects/sources/trails-hello-world node server.js

Description

Hello there. sorry for creating this pull request. for a while i was following you guys and i liked the idea behind trails js. But there is a fact that i have some ideas about implementation and have things i wanna add to trails frameworks and generators. I think this repository and other trailsjs related repositories are being inactive. so before forking whole project and starting to go my own way with it wanted to know whats up with you guys? you have any plans in mind which i can possibly help with? to avoid overlapping works

Issues

• resolves #???

I have setup a trails application through yo trails.But when I start my application It is giving me this error. I have installed fresh application

Environment

• node version: 8.11.0
• trails version: 3.1.0
• operating system: windows 10

Issue Description

Hi, I have a problem with my installation...

https://imgur.com/a/R5l8KER

https://pastebin.com/9HgkrWeS

9 http fetch GET 404 https://registry.npmjs.org/trailpack-other 1169ms 10 silly fetchPackageMetaData error for trailpack-other@^3 404 Not Found: trailpack-other@^3 11 silly fetchPackageMetaData error for trailpack-other@^3 404 Not Found: trailpack-other@^3 12 http fetch GET 404 https://registry.npmjs.org/trailpack-none 2350ms 13 silly fetchPackageMetaData error for trailpack-none@^3 404 Not Found: trailpack-none@^3 14 timing stage:rollbackFailedOptional Completed in 1ms 15 timing stage:runTopLevelLifecycles Completed in 2656ms 16 verbose stack Error: 404 Not Found: trailpack-other@^3

Environment

• node version: 10.2.1
• trails version: 3
• operating system: WINDOWS

@jaumard I think I found another issue with the config.

On trailpack-koa I have:

// index.js
...
configure() {
...
// line 56
this.app.config.set('web', result[1])
...
}
...

which updates the current configuration with various defaults and checks using JOI.

Now if on my app or another trailpack I see this result:

this.app.config.get('web.server') // undefined
this.app.config.get.web.server // 'koa'

I've been careful to ask for this config value after trailpack-koa 's configure method is completed.