我的站点是使用Gatsby建立的,并持续部署Netlify。我已经两个月没碰过我的盖茨比网站了。因此,当我运行更新、添加新内容和部署时,在Netlify构建上遇到了一个中断错误。
尝试了很多事情,花了太多时间在上面。最初我只使用NPM。在坚持了一段时间之后,我按照一些在线线程的建议,转到了纱线。现在使用yarn得到不同的错误消息,但部署到Netlify仍然没有成功。
这可能是一些愚蠢的简单的事情。我知道我以前也遇到过部署/构建的问题,但...我在这一点上不知所措...
Gatsby Develop
和Gatsby Build
都可以工作。gatsby build
命令master
和转纱
分支是一个热乱七八糟的。正在处理PR#58以解决此部署问题注意:我还把这篇文章发到了Reddit:https://www.reddit.com/r/gatsbyjs/comments/bnfqij/help_netlify_deploy_fails_on_gatsby_build/
下面是尝试构建Netlify之后的部署细节。我在代码块之后链接了一个屏幕截图,以便您可以看到错误高亮显示。
10:42:15 PM: Build ready to start
10:42:18 PM: build-image version: 8e315e54bc4032a32e73290be556cde4f8348c12
10:42:18 PM: build-image tag: v2.8.2
10:42:18 PM: buildbot version: 1c5d5da2a8a19e94f07a53f82f5c9b010bad1249
10:42:18 PM: Fetching cached dependencies
10:42:18 PM: Failed to fetch cache, continuing with build
10:42:18 PM: Starting to prepare the repo for build
10:42:18 PM: No cached dependencies found. Cloning fresh repo
10:42:18 PM: git clone git@github.com:heyspacetime/spacetime-gatsby
10:42:22 PM: Preparing Git Reference pull/58/head
10:42:22 PM: Found netlify.toml. Overriding site configuration
10:42:22 PM: Starting build script
10:42:22 PM: Installing dependencies
10:42:23 PM: Downloading and installing node v8.16.0...
10:42:23 PM: Downloading https://nodejs.org/dist/v8.16.0/node-v8.16.0-linux-x64.tar.xz...
10:42:24 PM: 0.3%
10:42:24 PM:
###########
10:42:24 PM: 16.3%
10:42:24 PM:
##########################################################
10:42:24 PM: 81.6%
10:42:24 PM:
#######################################
10:42:24 PM: ################################# 100.0%
10:42:24 PM: Computing checksum with sha256sum
10:42:24 PM: Checksums matched!
10:42:26 PM: Now using node v8.16.0 (npm v6.4.1)
10:42:26 PM: Attempting ruby version 2.3.6, read from environment
10:42:27 PM: Using ruby version 2.3.6
10:42:28 PM: Using PHP version 5.6
10:42:28 PM: Started restoring cached node modules
10:42:28 PM: Finished restoring cached node modules
10:42:28 PM: Started restoring cached yarn cache
10:42:28 PM: Finished restoring cached yarn cache
10:42:28 PM: Installing yarn at version 1.5.1
10:42:28 PM: Installing Yarn!
10:42:28 PM: > Downloading tarball...
10:42:28 PM: [1/2]: https://yarnpkg.com/downloads/1.5.1/yar
10:42:28 PM: n-v1.5.1.tar.gz --> /tmp/yarn.tar.gz.unnZulZpgP
10:42:28 PM: % Total % Recei
10:42:28 PM: ved % Xferd Average Speed Time Time Time Curr
10:42:28 PM: ent
10:42:28 PM: Dload Upload Total Spent
10:42:28 PM: Left Speed
10:42:28 PM:
0
10:42:28 PM: 0 0 0 0 0 0 0 --:--:-- --:-
10:42:28 PM: -:-- --:--:-- 0
10:42:28 PM:
100 91 100 91 0 0 511
10:42:28 PM: 0 --:--:-- --:--:-- --:--:-- 514
10:42:28 PM:
0 0 0 608 0 0 1591 0 --:
10:42:28 PM: --:-- --:--:-- --:--:-- 1591
10:42:28 PM:
100 914k 100 914k 0 0 1226k 0 --:--:-- --:-
10:42:28 PM: -:-- --:--:-- 1226k
10:42:28 PM: [2/2]: https://yarnpkg.co
10:42:28 PM: m/downloads/1.5.1/yarn-v1.5.1.tar.gz.asc --> /tmp/yarn.tar.gz.unnZ
10:42:28 PM: ulZpgP.asc
10:42:29 PM:
100 95 100 95 0 0 2061 0 --:--:-
10:42:29 PM: - --:--:-- --:--:-- 2061
10:42:29 PM:
0 0 0 612 0 0 3939
10:42:29 PM: 0 --:--:-- --:--:-- --:--:-- 3939
10:42:29 PM:
0 832 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
10:42:29 PM:
100 832 100 832 0 0 3750
10:42:29 PM: 0 --:--:-- --:--:-- --:--:-- 812k
10:42:29 PM: > Verifying integrity...
10:42:29 PM: gpg: Signature made Mon 26 Feb 2018 07:01:19 PM UTC using RSA key ID B6FF4DE3
10:42:29 PM: gpg: Good signature from "Yarn Packaging <yarn@dan.cx>"
10:42:29 PM: gpg: Note: This key has expired!
10:42:29 PM: Primary key fingerprint: 72EC F46A 56B4 AD39 C907 BBB7 1646 B01B 86E5 0310
10:42:29 PM: Subkey fingerprint: E219 30C4 D0A4 AA46 1858 1F7A E074 D16E B6FF 4DE3
10:42:29 PM: > GPG signature looks good
10:42:29 PM: > Extracting to ~/.yarn...
10:42:29 PM: > Adding to $PATH...
10:42:29 PM: > We've added the following to your /opt/buildhome/.profile
10:42:29 PM: > If this isn't the profile of your current shell then please add the following to your correct profile:
10:42:29 PM: export PATH="$HOME/.yarn/bin:$HOME/.config/yarn/global/node_modules/.bin:$PATH"
10:42:29 PM:
10:42:30 PM: > Successfully installed Yarn 1.5.1! Please open another terminal where the `yarn` command will now be available.
10:42:30 PM: Installing NPM modules using Yarn version 1.5.1
10:42:31 PM: yarn install v1.5.1
10:42:31 PM: [1/4] Resolving packages...
10:42:33 PM: [2/4] Fetching packages...
10:42:55 PM: info fsevents@1.2.9: The platform "linux" is incompatible with this module.
10:42:55 PM: info "fsevents@1.2.9" is an optional dependency and failed compatibility check. Excluding it from installation.
10:42:55 PM: [3/4] Linking dependencies...
10:42:55 PM: warning " > a11y-react-emoji@1.0.0" has incorrect peer dependency "react@16.7.0".
10:42:55 PM: warning "gatsby > pnp-webpack-plugin > ts-pnp@1.1.2" has unmet peer dependency "typescript@*".
10:42:55 PM: warning "gatsby-plugin-transition-link > babel-preset-gatsby-package > @babel/plugin-proposal-optional-chaining@7.2.0" has unmet peer dependency "@babel/core@^7.0.0-0".
10:42:55 PM: warning "gatsby-plugin-transition-link > babel-preset-gatsby-package > @babel/preset-flow@7.0.0" has unmet peer dependency "@babel/core@^7.0.0-0".
10:42:55 PM: warning "gatsby-plugin-transition-link > babel-preset-gatsby-package > @babel/plugin-proposal-optional-chaining > @babel/plugin-syntax-optional-chaining@7.2.0" has unmet peer dependency "@babel/core@^7.0.0-0".
10:43:05 PM: [4/4] Building fresh packages...
10:43:12 PM: success Saved lockfile.
10:43:12 PM: Done in 41.23s.
10:43:12 PM: NPM modules installed using Yarn
10:43:12 PM: Started restoring cached go cache
10:43:12 PM: Finished restoring cached go cache
10:43:12 PM: Installing Go version 1.10
10:43:18 PM: unset GOOS;
10:43:18 PM: unset GOARCH;
10:43:18 PM: export GOROOT='/opt/buildhome/.gimme_cache/versions/go1.10.linux.amd64';
10:43:18 PM: export PATH="/opt/buildhome/.gimme_cache/versions/go1.10.linux.amd64/bin:${PATH}";
10:43:18 PM: go version >&2;
10:43:18 PM: export GIMME_ENV="/opt/buildhome/.gimme_cache/env/go1.10.linux.amd64.env"
10:43:18 PM: go version go1.10 linux/amd64
10:43:18 PM: Installing missing commands
10:43:18 PM: Verify run directory
10:43:18 PM: Executing user command: npm run build
10:43:18 PM: > Spacetime@1.0.0 build /opt/build/repo
10:43:18 PM: > gatsby build
10:43:20 PM: success open and validate gatsby-configs — 0.011 s
10:43:21 PM: success load plugins — 1.030 s
10:43:21 PM: success onPreInit — 0.118 s
10:43:21 PM: success delete html and css files from previous builds — 0.005 s
10:43:21 PM: success initialize cache — 0.008 s
10:43:21 PM: success copy gatsby files — 0.022 s
10:43:21 PM: success onPreBootstrap — 0.004 s
10:43:22 PM: success source and transform nodes — 0.413 s
10:43:22 PM: success building schema — 0.226 s
10:43:22 PM: success createPages — 0.018 s
10:43:22 PM: success createPagesStatefully — 0.072 s
10:43:22 PM: success onPreExtractQueries — 0.002 s
10:43:22 PM: success update schema — 0.024 s
10:43:22 PM: success extract queries from components — 0.078 s
10:43:22 PM: success run static queries — 0.001 s
10:43:22 PM: success run page queries — 0.019 s — 20/20 1114.65 queries/second
10:43:22 PM: success write out page data — 0.006 s
10:43:22 PM: success write out redirect data — 0.001 s
10:43:23 PM: success Build manifest and related icons — 0.776 s
10:43:23 PM: success onPostBootstrap — 0.778 s
10:43:23 PM: info bootstrap finished - 5.200 s
10:43:42 PM: error Generating JavaScript bundles failed
10:43:42 PM:
10:43:42 PM: Error: ./src/assets/stylesheets/styles.scss
10:43:42 PM: Module build failed (from ./node_modules/gatsby/node_modules/mini-css-extract- plugin/dist/loader.js):
10:43:42 PM: ModuleBuildError: Module build failed (from ./node_modules/sass-loader/lib/loa der.js):
10:43:42 PM: Error: ENOENT: no such file or directory, scandir '/opt/build/repo/node_module s/node-sass/vendor'
10:43:42 PM: at Object.fs.readdirSync (fs.js:904:18)
10:43:42 PM: at Object.getInstalledBinaries (/opt/build/repo/node_modules/node-sass/lib /extensions.js:131:13)
10:43:42 PM: at foundBinariesList (/opt/build/repo/node_modules/node-sass/lib/errors.js :20:15)
10:43:42 PM: at foundBinaries (/opt/build/repo/node_modules/node-sass/lib/errors.js:15: 5)
10:43:42 PM: at Object.module.exports.missingBinary (/opt/build/repo/node_modules/node- sass/lib/errors.js:45:5)
10:43:42 PM: at module.exports (/opt/build/repo/node_modules/node-sass/lib/binding.js:1 5:30)
10:43:42 PM: at Object.<anonymous> (/opt/build/repo/node_modules/node-sass/lib/index.js :14:35)
10:43:42 PM: at Module._compile (/opt/build/repo/node_modules/v8-compile-cache/v8-compi le-cache.js:178:30)
10:43:42 PM: at Object.Module._extensions..js (module.js:664:10)
10:43:42 PM: at Module.load (module.js:566:32)
10:43:42 PM: at tryModuleLoad (module.js:506:12)
10:43:42 PM: at Function.Module._load (module.js:498:3)
10:43:42 PM: at Module.require (module.js:597:17)
10:43:42 PM: at require (/opt/build/repo/node_modules/v8-compile-cache/v8-compile-cache .js:159:20)
10:43:42 PM: at Object.sassLoader (/opt/build/repo/node_modules/sass-loader/lib/loader. js:46:72)
10:43:42 PM: at runLoaders (/opt/build/repo/node_modules/gatsby/node_modules/webpack/li b/NormalModule.js:301:20)
10:43:42 PM: at /opt/build/repo/node_modules/loader-runner/lib/LoaderRunner.js:367:11
10:43:42 PM: at /opt/build/repo/node_modules/loader-runner/lib/LoaderRunner.js:233:18
10:43:42 PM: at runSyncOrAsync (/opt/build/repo/node_modules/loader-runner/lib/LoaderRu nner.js:143:3)
10:43:42 PM: at iterateNormalLoaders (/opt/build/repo/node_modules/loader-runner/lib/Lo aderRunner.js:232:2)
10:43:42 PM: at Array.<anonymous> (/opt/build/repo/node_modules/loader-runner/lib/Loade rRunner.js:205:4)
10:43:42 PM: at Storage.finished (/opt/build/repo/node_modules/enhanced-resolve/lib/Cac hedInputFileSystem.js:43:16)
10:43:42 PM: at provider (/opt/build/repo/node_modules/enhanced-resolve/lib/CachedInput FileSystem.js:79:9)
10:43:42 PM: at /opt/build/repo/node_modules/graceful-fs/graceful-fs.js:90:16
10:43:42 PM: at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:511:3)
10:43:42 PM: @ ./src/components/layout.js 6:0-43
10:43:42 PM: @ ./src/pages/services/technical-seo.js
10:43:42 PM: @ ./.cache/async-requires.js
10:43:42 PM: @ ./.cache/production-app.js
10:43:42 PM:
10:43:42 PM: npm
10:43:42 PM: ERR! code ELIFECYCLE
10:43:42 PM: npm ERR!
10:43:42 PM: errno 1
10:43:42 PM: npm
10:43:42 PM: ERR! Spacetime@1.0.0 build: `gatsby build`
10:43:42 PM: npm ERR! Exit status 1
10:43:42 PM: npm ERR!
10:43:42 PM: npm ERR! Failed at the Spacetime@1.0.0 build script.
10:43:42 PM: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
10:43:43 PM: npm
10:43:43 PM: ERR! A complete log of this run can be found in:
10:43:43 PM: npm ERR! /opt/buildhome/.npm/_logs/2019-05-11T03_43_42_997Z-debug.log
10:43:43 PM: Skipping functions preparation step: no functions directory set
10:43:43 PM: Caching artifacts
10:43:43 PM: Started saving node modules
10:43:43 PM: Finished saving node modules
10:43:43 PM: Started saving yarn cache
10:43:43 PM: Finished saving yarn cache
10:43:43 PM: Started saving pip cache
10:43:43 PM: Finished saving pip cache
10:43:43 PM: Started saving emacs cask dependencies
10:43:43 PM: Finished saving emacs cask dependencies
10:43:43 PM: Started saving maven dependencies
10:43:43 PM: Finished saving maven dependencies
10:43:43 PM: Started saving boot dependencies
10:43:43 PM: Finished saving boot dependencies
10:43:43 PM: Started saving go dependencies
10:43:44 PM: Finished saving go dependencies
10:43:46 PM: Error running command: Build script returned non-zero exit code: 1
10:43:46 PM: Failing build: Failed to build site
10:43:46 PM: failed during stage 'building site': Build script returned non-zero exit code: 1
10:43:46 PM: Finished processing build request in 1m28.562451072s
10:43:46 PM: Shutting down logging, 0 messages pending
https://user-images.githubusercontent.com/4457883/57573280-F61ABE00-73EA-11E9-8AA9-673F32572202.png
我希望盖茨比网站能够建立在部署到Netlify的基础上。master
分支是我的生产站点,但Netlify也为分支创建测试构建。
你试过告诉Netlify清除缓存并重建吗?这个错误看起来您的怀疑是正确的,而且它没有安装node-sass
。
如果您转到Netlify dashboard>Deploys,应该会有一个“触发器部署”下拉列表提供此选项。
如果这不起作用,请尝试删除yarn.lock
并重新安装依赖项,以使Netlify能够获取所有内容的新副本。
我在部署gatsby启动的模板时遇到了这个错误,很可能对您也是一样的。所以默认情况下,我的“构建命令”在“netlify.toml”文件中设置为“纱构建”。这与Netlify(即gatsby build)上设置的build命令冲突。我只是将NetLify.toml修改为下面的代码,将“Yarn构建”改为“Gatsby构建”。
null
[build]
publish = "public"
command = "gatsby build"
[build.environment]
YARN_VERSION = "1.3.2"
YARN_FLAGS = "--no-ignore-optional"
部署到 Netlify 是一个低成本选项,可以快速在线获取 statically generated 的Nuxt.js网站。 该过程的核心在部署期间利用 nuxt generate 命令将Nuxt.js应用程序的静态版本构建到 dist 目录中。 然后将此目录的内容部署到生产URL。 入门 按 Netlify 仪表板上的 "New site from Git" 按钮。使用存储库主机进行身份验证,选
十构建部署 待更新……
我试图使用Fabric8 Maven插件部署示例项目。https://github.com/jbossdemocentral/katacoda-fuse-getting-started.git 我在远程机器中有一个启动并运行的Openshift环境,我正在使用“oc登录…”连接到它 本地开发机器设置:有docker,maven。已安装oc。 当我从命令提示符下运行示例项目“mvn fabric8:
我在本地有一个Spring Boot REST API。 它正在成功地生成。当我运行mvn clean package时,war文件在本地。 现在我想把它部署到Heroku。 这些就是我所做的步骤。 > 将代码上传到github respository。比如说\myrestapi。 打开终端以运行Heroku CLI命令 登录heroku heroku登录 运行命令在heroku上创建应用程序 这
部署到netlify失败并出现错误:,但当我使用在本地构建时它可以工作(与netlify相同)。无法解析的包直接从github安装,而不是其他包。 package.json: netlify日志: KeyNavigation.ts: 为什么部署在netlify失败,而不是在本地?