You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running in non-interactive mode, for example, like this:
npx create-local-addon "My Product Name" directory-name
The productname argument isn't correctly parsed, with the second word of the string being interpreted as the directory name. See this screenshot for more details:
Note: Running the command in interactive mode (ie, when create-local-addon prompts you for productname and directoryname) does work.
The text was updated successfully, but these errors were encountered:
That is really odd. I don't seem to get that issue on my end with the same steps. A check of the package.json confirms the directory and package are named correctly, too. Could it be a quote issue — like using directional quotation marks instead of standard/straight quotes? I do not believe I tested it with these variations, but it was just a random thought.
I have included my output below:
(I also tried running npx create-local-addon "My directory-name Name" directory-name-next just to see if the directory name being included in the name would somehow trip it up, but it worked fine.)
When running in non-interactive mode, for example, like this:
The
productname
argument isn't correctly parsed, with the second word of the string being interpreted as the directory name. See this screenshot for more details:Note: Running the command in interactive mode (ie, when
create-local-addon
prompts you forproductname
anddirectoryname
) does work.The text was updated successfully, but these errors were encountered: