Unable to generate custom metadata with example script "scriptlibphonenumber-metadata"
See original GitHub issueHey Nikolay
I followed the new docs for generating a set of custom metadata but the example script provided in the docs fails to execute with the following error: sh: libphonenumber-generate-metadata: command not found
. This is the script I’ve included into the package.js
: "libphonenumber-metadata": "libphonenumber-generate-metadata metadata.min.json --countries DE --extended",
.
What works for me though is the following script: "libphonenumber-metadata": "node bin/update-metadata metadata.min.json --countries DE --extended",
.
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Custom Metadata relationship - unable to create
You must first create a Lookup relationship, populate the lookup field with data in all records, and then change the relationship type to...
Read more >Custom Metadata Types Implementation Guide
Subscribers can't add custom metadata records to installed custom metadata types that are protected. To allow subscribers to create.
Read more >Access Custom Metadata Records Programmatically
Use SOQL to access your custom metadata types and to retrieve the API names of the records of those types.
Read more >How to Retrieve and Deploy Custom Metadata Types using ANT
Sample of Package.xml to deploy Custom Metadata Types ... not able to use Migration tools to import export records into custom settings.
Read more >Set custom metadata - Compute Engine - Google Cloud
For example, SSH keys are stored as custom metadata under the ssh-keys key. ... as Cloud Storage, and provide the startup script URL...
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 FreeTop 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
Top GitHub Comments
Yeah, that one was a bit misleading. I rephrased that section.
Ah, I got it. There is no issue with yarn.
I was doing all the steps in the libphonenumber-js root folder which I’ve downloaded as a zip archive. I got confused by the section Metadata generation which requires you to fork this project in order to generate metadata.