Update docs to show how Serverless can be installed and used locally
See original GitHub issueThis is a Feature Proposal
Description
Instead of globally installing Serverless, could we only globally install a CLI shim that checks the current directory’s node_modules
for Serverless? This way we can add a devDependency
directly to our package.json
and lock it from there rather than having to do it in serverless.yml
.
There should be little-to-no changes from a developer’s perspective.
Issue Analytics
- State:
- Created 6 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Setting Up Serverless Framework With AWS
You can upgrade the CLI later by running the same command: npm install -g serverless . To upgrade to a specific major version,...
Read more >Installing the AWS SAM CLI
To learn how to manage a currently installed version of the AWS SAM CLI, including how to upgrade, uninstall, or manage nightly builds,...
Read more >HubSpot CLI commands
You can install HubSpot local development tools either globally ... Works similar to using standard ls to view your current directory on ...
Read more >Serverless computing
Google Cloud serverless enables you to build and deploy functions and applications using a fully managed end-to-end serverless platform.
Read more >Getting Started - Twilio Serverless Toolkit
The Twilio Serverless Toolkit allows you to locally develop and deploy Twilio ... If you are already using the Twilio CLI, you can...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Nice discussion! I updated the title and added some labels.
I agree that it would be worth to have this somewhere in the docs.
/cc @brianneisler
I was aware of that feature and it was exactly that which got me wondering why I couldn’t just specify it in
package.json
instead. The problem with specifying theframeworkVersion
is you’d still need to up/downgrade your global installed version to deploy a project.Leave dependency/version management to the tools that do it best IMO.