Move version declarations out of component type property about components

[laardee]

With dependencies block, we could have a similar installation flow as npm or yarn. components add foo would fetch the foo component, or just headers/metadata to validate that the component exists and is compatible with current version of components, from an external registry and add it to dependencies block. Using named versions like in the @jrmacks latter suggestion, could be then implemented with, e.g. -n flag -> components add [email protected] -n oldFoo would add the foo as oldFoo to the dependencies.

[jrmacks]

Excellent explanation of the problem and agree with your approach. One scenario to consider is if in one of your components you explicitly want to reference a different version. Perhaps it may be good to keep the current logic in place as an override to the root dependencies block?

Example:

type: my-component

dependencies:
  foo: ^1.0.0 

components:
  foo1:
    type: foo # uses root v1.0.0
  foo2:
    type: [email protected]  # overriding the root dependency version

Or setup the dependencies block to use variables.

Example:

type: my-component

dependencies:
  foo: [email protected]
  oldFoo: [email protected]

components:
  foo1:
    type: foo # uses v1.0.0
  foo2:
    type: oldFoo # v0.9.1

[iDVB]

Just taking a completely newb look at this...
Is there a reason you'd even want to mention per/component versioning in the yml, and not use existing npm/yarn (package.json)?

Similar to SLS plugins.... there is no mention to the version of the plugins in the yml. (AFAIK)

[brianneisler]

@iDVB excellent question. Our actual hope is to prevent exposing node/npm entirely. A lot of the ecosystem includes other languages besides node js. The goal is basically to be able to use serverless without even realizing that it uses node js under the hood. Therefore the only time you would have to interact with node/npm is if you are either...

A) writing a node js serverless app
B) writing a plugin
C) writing a component that requires code

If you are writing a python, go, java, etc serverless app though, you should have no requirement to install or interact with node js. This makes the tooling much more friendly to non-node js developers.

[eahefnawy]

closing this as we've made a complete rewrite of the core and this issue is no longer applicable.