split out detectors and templates, invite contributors

[swyxio]

(slack mention: https://netlify.slack.com/archives/CGW2Y6XPH/p1553102448110100)

we dont want to re-release the CLI and netliy dev plugin every time we add a new detector (or template).

we should use https://www.npmjs.com/package/live-plugin-manager or https://www.npmjs.com/package/pacote to make this scale.

however we should also have some consideration for offline dev experience.

[swyxio]

@calavera the approach i propose for this is to maintain two separate monorepos, one for detectors, one for templates. each monorepo contains all detectors and all templates (this is fine for our current scale).

we will use pacote as it is far more active (but lower level).

• when netlify dev runs, we install the detector monorepo in the .netlify/detectors folder and require it
• when netlify functions:create runs, we install the templates monorepo in the .netlify/function-templates folder and require it

this solves our re-releasing problem. it should also be performant and offline-ready because of pacote's caching (used by npm's cli itself)

does this sound ok? it is the simplest approach and i wanted to address this before we launch.

[calavera]

does this sound ok? it is the simplest approach and i wanted to address this before we launch.

sounds good to me

[swyxio]

or maybe we should just use https://www.npmjs.com/package/gh-release-fetch 😅

[swyxio]

tried to do this today, however gh-release-fetch requires asset artefacts, so i turned to the other two. both of them do NOT work offline as promised, which i am very disappointed about. wasted an hour or two.

[swyxio]

note that its useful here netlify/build#12

[swyxio]

https://github.com/zeit/now-builders/blob/99c7a58d318ff5e4064ace0be8d788698c7b22de/packages/now-static-build/src/index.ts#L166

[erezrokah]

Closing in favor of #1495