Create Function - package.json name does not match regexp warning

[GeorgeBellTMH]

Before opening, please confirm:

• I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
• I have searched for duplicate or closed issues.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

latest

Amplify CLI Version

latest

What operating system are you using?

macOS

Amplify Categories

function

Amplify Commands

add

Describe the bug

When you create an amplify function with capitals, there is a warning that appears for the name field in package.json that is created...

String does not match the pattern of "^(?:@[a-z0-9-~][a-z0-9-.]*/)?[a-z0-9-][a-z0-9-.~]*$".

Expected behavior

No warning should appear...name field should be modified to lowercase...

Reproduction steps

Create a function called testFunction

GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information

No response

[josefaidt]

Hey @GeorgeBellTMH 👋 thanks for raising this! I also see this warning from npm regarding an invalid name field value. Thankfully this does not impact our deployments or usage, however it does not follow the spec for package.json name field. Marking this as a feature request to force the package name to all lowercase when adding a function with capital letters in the name.

[studpeps]

Hey @GeorgeBellTMH and @josefaidt, I am trying to reproduce the issue but have been unable to, has this been arising when deploying or when creating the function locally
I did the following steps to produce the bug:

$ amplify add function
? Select which capability you want to add: Lambda function (serverless function)
? Provide an AWS Lambda function name: testFunction
? Choose the runtime that you want to use: NodeJS
? Choose the function template that you want to use: Hello World

Available advanced settings:

• Resource access permissions
• Scheduled recurring invocation
• Lambda layers configuration
• Environment variables configuration
• Secret values configuration

? Do you want to configure advanced settings? No
? Do you want to edit the local lambda function now? No
Successfully added resource testFunction locally.

It gives me a success message for lambda function

[josefaidt]

Hey @studpeps 👋 this is an npm warning and does not impact creation or pushes of the Lambda function. It can be found in the function's package.json file:

Reference for package.json "name" specification

[studpeps]

Oh yes right, thank you @josefaidt

[cjihrig]

I've opened #8051 as a revert. I do think we should address this issue, but I think we can do it in a less breaking way.

[GeorgeBellTMH]

At the least can we implement this on new functions? I would also suggest asking if it should be fixed on updates...there doesn't seem to be a lot of good reasons to have an incorrect package.json...

[fossamagna]

I've opened #8051 as a revert. I do think we should address this issue, but I think we can do it in a less breaking way.

Hey @cjihrig. I considered it as follows.

• We can contain upper case characters in function name as before
• Only name in package.json will be changed to lower case.

What do you think on this?

[cjihrig]

@fossamagna that could potentially work.