⚡ Serverless Framework – Effortlessly build apps that auto-scale, incur zero costs when idle, and require minimal maintenance using AWS Lambda and other managed cloud services.
I have several questions about the binary files that binary.js installs when I run the serverless (sls) command, and the JavaScript files (such as sf-core.js) that the binary files appear to install under $HOME/.serverless/releases/x.y.z/.
Q.1 Under the following conditions, if I have already run the serverless (sls) command once and installed a binary file named serverless--- (e.g. serverless-linux-amd64-0.0.2) locally using run.js and binary.js, is it guaranteed that it will not be overwritten the second time onwards? (I read binary.js and think the specifications are as written above, but I just want to confirm if my understanding is correct.)
Condition 1: Always run on the same OS type and OS arch (e.g. linux-amd64)
Condition 2: The version of the Serverless Framework is completely fixed in the frameworkVersion in serverless.yml (e.g. frameworkVersion: 4.4.18)
Q.2 What does the binary file serverless--- (e.g. serverless-linux-amd64-0.0.2) do? (I assume that this binary file reads the frameworkVersion: x.y.z specified in serverless.yml, if any, and then downloads the corresponding version of the Serverless Framework JavaScript files (such as sf-core.js) from the server you manage, and installs it under $HOME/.serverless/releases/x.y.z/. But is that correct? Does this binary file do anything else?)
Q.3 Is the source code for serverless--- available for viewing?
Q.4 Will the contents under the $HOME/.serverless/releases/x.y.z/ will be exactly the same as long as the frameworkVersion: x.y.z specified in serverless.yml does not change?)
Q.5 By default, JavaScript files (such as sf-core.js) seem to be installed in $HOME/.serverless/releases/x.y.z/, but can I change this path to a path of my choice? For example, can I change it to the same directory as binary.js as follows?
Issue description
I have several questions about the binary files that binary.js installs when I run the serverless (sls) command, and the JavaScript files (such as sf-core.js) that the binary files appear to install under
$HOME/.serverless/releases/x.y.z/.Q.1 Under the following conditions, if I have already run the serverless (sls) command once and installed a binary file named serverless--- (e.g.
serverless-linux-amd64-0.0.2) locally using run.js and binary.js, is it guaranteed that it will not be overwritten the second time onwards? (I read binary.js and think the specifications are as written above, but I just want to confirm if my understanding is correct.)linux-amd64)frameworkVersion: 4.4.18)Q.2 What does the binary file serverless--- (e.g.
serverless-linux-amd64-0.0.2) do? (I assume that this binary file reads theframeworkVersion: x.y.zspecified in serverless.yml, if any, and then downloads the corresponding version of the Serverless Framework JavaScript files (such as sf-core.js) from the server you manage, and installs it under$HOME/.serverless/releases/x.y.z/. But is that correct? Does this binary file do anything else?)Q.3 Is the source code for serverless--- available for viewing?
Q.4 Will the contents under the
$HOME/.serverless/releases/x.y.z/will be exactly the same as long as theframeworkVersion: x.y.zspecified in serverless.yml does not change?)Q.5 By default, JavaScript files (such as sf-core.js) seem to be installed in
$HOME/.serverless/releases/x.y.z/, but can I change this path to a path of my choice? For example, can I change it to the same directory as binary.js as follows?Context
No response