将Font Awesome Pro与Google App Engine一起使用



如何让Font Awesome Pro在标准环境中在Google的App Engine上运行?

我已经包含了带有正确注册表设置和身份验证令牌的 .npmrc 文件:

@fortawesome:registry=https://npm.fontawesome.com/
//npm.fontawesome.com/:_authToken=XXXXXXXXXXXXXXXX

但是,在部署代码后,我得到以下结果:

Step #1 - "builder": npm ERR! code E404
Step #1 - "builder": npm ERR! 404 Not Found - GET https://registry.npmjs.org/@fortawesome%2ffontawesome-pro - Not found
Step #1 - "builder": npm ERR! 404 
Step #1 - "builder": npm ERR! 404  '@fortawesome/fontawesome-pro@^5.12.1' is not in the npm registry.
Step #1 - "builder": npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
Step #1 - "builder": npm ERR! 404 It was specified as a dependency of 'workspace'
Step #1 - "builder": npm ERR! 404 
Step #1 - "builder": npm ERR! 404 Note that you can also install from a
Step #1 - "builder": npm ERR! 404 tarball, folder, http url, or git url.
Step #1 - "builder": 
Step #1 - "builder": npm ERR! A complete log of this run can be found in:
Step #1 - "builder": npm ERR!     /builder/home/.npm/_logs/2020-02-10T16_36_28_563Z-debug.log
Step #1 - "builder": 
Step #1 - "builder": ERROR    error: `gen_package_lock` returned code: 1
Step #1 - "builder": INFO     gen_package_lock took 13 seconds
Step #1 - "builder": INFO     builder initialization took 13 seconds
Step #1 - "builder": INFO     full build took 13 seconds
Step #1 - "builder": ERROR    `gen_package_lock` had stderr output:
Step #1 - "builder": npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
Step #1 - "builder": npm ERR! code E404
Step #1 - "builder": npm ERR! 404 Not Found - GET https://registry.npmjs.org/@fortawesome%2ffontawesome-pro - Not found
Step #1 - "builder": npm ERR! 404 
Step #1 - "builder": npm ERR! 404  '@fortawesome/fontawesome-pro@^5.12.1' is not in the npm registry.
Step #1 - "builder": npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
Step #1 - "builder": npm ERR! 404 It was specified as a dependency of 'workspace'
Step #1 - "builder": npm ERR! 404 
Step #1 - "builder": npm ERR! 404 Note that you can also install from a
Step #1 - "builder": npm ERR! 404 tarball, folder, http url, or git url.
Step #1 - "builder": 

显然,它无法识别 .npmrc,因为 URL 端点仍然指向 https://registry.npmjs.org。有什么建议吗?

发现这是因为我的 .gcloudignore 文件。我需要排除被忽略的 .npmrc 文件。

相关内容

最新更新