docs(readme): Update the README for latest serverless v2 and upcoming v3

[mnapoli]

Description

As mentioned in the discussion (#155 (comment)), Serverless Framework v2 and (upcoming) v3 support .env for ${env:xxx} variables via an option in the config.

That makes part of this plugin redundant. Especially since the plugin will no longer be able to load environment variables in the process.

However, this plugin is still useful to automatically inject all .env variables into functions.

So here is what we can do/recommend users:

• to use ${env:xxx} with .env, use the native Serverless Framework feature
• to import all .env variables into functions, use this plugin

See serverless/serverless#10495

I've updated the README to make this clearer. Let me know if that clarifies everything for v3?

[mnapoli]

@neverendingqs Since v3 was released last week would you have time to merge this pull request?

That would make upgrading more clear/easy for users.

[neverendingqs]

@neverendingqs Since v3 was released last week would you have time to merge this pull request?

That would make upgrading more clear/easy for users.

Sorry I will need to find time to take a look later. Initial thought is that this information should maybe go into a FAQ, since (I suspect) that adoption of v3 hasn't hit critical mass yet.

[mnapoli]

V3 usage is already at 17% of the whole userbase. It's growing very fast.

[mnapoli]

Hi @neverendingqs, quick reminder about this PR :)

Have a great weekend!

[shadrech]

On a side note, one feature which I think they should support for the useDotenv feature is the path option. This way we can dictate where the .env file can be to be used by the plugin. This is especially useful in monorepos as in my case

[neverendingqs]

Hey sorry finally got a chance to sit down and take a look.

[jayarjo]

What about Serverless v4? This plugin is still very actual from what I see.