if a domain

Importent Hooks

• app._router.stack === []
  the Complet stack of registered middelware for a express app
• express.Router().stack === []
  the Complet stack of registered middelware for a express app router

remove change reorder middelware as needed and export it as own app.

steal server demonstrates that powerfull via its use of done-serve 👯‍♂️

https://github.com/steal-server/server/blob/master/lib/helpers.js

replace with fsexists checks.

if it has a package.json lets serve what ever is files is set to

We need to integrate our C Server directly into this

then default proxy to this and make config option for static files and other proxys directly in this.

so we default to this but! allow the user to configure something totally diffrent we don't block that!

So for every host reflect config in realtime! via a express direktspeed framework middelware

maybe document the mruby support but i think we should first finish experiment DIREKTSPEED-X985332-9 wich is about the direct nativ nodejs bindings.

TODO:

• Automatic creates letsEncrypt certs and manages renew (by directory config Zero config mode)
• Zero Config Mode
• Per Project Zero Config Mode (package.json)
• PreProcessor Chain Zero Config
• Host stealjs / donejs Projects Production Ready Scale able
• Outperforms NGINX by up to 200% in some deciplines 100% minimum.
• hosting donejs projects live dev.host and production.host realtime sync to find compiling errors more fast
• Option to auto preprocess ( build donejs projects if needed )
• ngrok support out of the box
• use same server for dev and production!
• Advanced Modules
  • Neuronal Network self Scaling (Enterprise Feature)
  • Neuronal Network self Defence (Takes Aktion on Cyber Attacks Pro Active Solution)
  • Neuronal Network Fraud Detection.

Line out in deep features like:

• http2 support cache aware push support

On registry https://registry.npmjs.org/, the "latest" version (v2.2.5) of dependency cross-spawn-async has the following deprecation notice:

cross-spawn no longer requires a build toolchain, use it instead

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about cross-spawn-async's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

Scan every folder under root/
find package.json if not exist assume default harp project

if finds package.json use it to find out if we are a express,feathers,donejs Application

if we are simply surfe that.

TODO: Find out what happens with individual listen stuff maybe make a master pollifil for that

steal-prerender could offer a middelware to link all modules from
the path

function npmls(cb) {
require('child_process').exec('npm ls --depth 0 --json', function(err, stdout, stderr) {
if (err) return cb(err)
cb(null, JSON.parse(stdout));
});
}
npmls(console.log);

npm.commands.ls(args, [silent,] callback)
console.log(Object.keys(require('./package.json').dependencies));

we will probally use rootRequire try catched

---- https://gist.github.com/branneman/8048520#comment-1412502
2. The Global

In your app.js:

global.__base = __dirname + '/';
In your very/far/away/module.js:

var Article = require(__base + 'app/models/article');

7. The Wrapper

Courtesy of @a-ignatov-parc. Another simple solution which increases obviousness, simply wrap the require() function with one relative to the path of the application's entry point file.

Place this code in your app.js, again before any require() calls:

global.rootRequire = function(name) {
return require(__dirname + '/' + name);
}
You can then require modules like this:

var Article = rootRequire('app/models/article');

Install some module:

npm install app-module-path --save
In your app.js, before any require() calls:

require('app-module-path').addPath(__dirname + '/app');

or Use NODE_PATH=. or project root for require

hacky method

process.env.NODE_PATH = __dirname;
require('module').Module._initPaths();

I've been using symlinks with the following structure:

/node_modules
/package.json
/src
  /node_modules
    /client -> ../client
    /server -> ../server
    /shared -> ../shared
  /client
    /apps
      /main
        /test
          main.spec.js
        index.js
    /modules
      /foo
        /test
          foo.spec.js
        index.js
  /server
    /apps
    /modules
  /shared

it also solves the problem of not know where the modules come from because all app modules have client/server/shared prefixes in require paths

Replace with fs-extra

At present we have one Project Type: [Prerender/Harp]

• Should add steal/donejs.
• Should add nodejs
• Should add php?
• Should add docker?
• Should add ?????

Allows to register routes in nginx when used as proxy for 404 requests dynamic

Routing Multi Server using ssr.js

Directory Structure
Project Directory
|
|--| server
|--| ssr.js
|--| public
|--| package.json

This issue provides visibility into Renovate updates and their statuses. Learn more

Rate Limited

These updates are currently rate limited. Click on a checkbox below to force their creation now.

• Update dependency chalk to v5
• Update dependency commander to v9
• Update dependency mime to v3
• Update dependency mocha to v10
• Update dependency node-fetch to v3

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• Update dependency send to ^0.18.0

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency nixt to v0.5.1
• Update dependency node-fetch to v2.6.7
• Update dependency request to v2.88.2
• Update Node.js to 4.9
• Update dependency es6-promise to v4.2.8
• Update dependency jshint to v2.13.4
• Update dependency mime to v2.6.0
• Update dependency mocha to v7.2.0
• Update dependency should to v13.2.3
• Update dependency async to v3
• Update dependency fs-extra to v10
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

The idea is to catch the first request process it then configure the real target and return its response
we should not get a secund req after that because the other new configured target takes over.