-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy to Netlify not working #87
Comments
@rileypetersen I was out in a small winter vacation but I'm back today and will try to provide a fix for your issue soon. |
I have another, possibly related issue. The error I am getting is this:
|
|
for me it throws an error to 5:13:23 PM: Build ready to start
5:13:27 PM: build-image version: b0258b965567defc4a2d7e2f2dec2e00c8f73ad6
5:13:27 PM: build-image tag: v3.4.1
5:13:27 PM: buildbot version: 648208d76731cd5bca75c1e9bc99d2032a1f1473
5:13:27 PM: Fetching cached dependencies
5:13:27 PM: Failed to fetch cache, continuing with build
5:13:27 PM: Starting to prepare the repo for build
5:13:28 PM: No cached dependencies found. Cloning fresh repo
5:13:28 PM: git clone https://github.com/QardsJs/qards
5:13:31 PM: Preparing Git Reference refs/heads/master
5:13:32 PM: Starting build script
5:13:32 PM: Installing dependencies
5:13:32 PM: Python version set to 2.7
5:13:34 PM: v12.18.0 is already installed.
5:13:34 PM: Now using node v12.18.0 (npm v6.14.4)
5:13:35 PM: Started restoring cached build plugins
5:13:35 PM: Finished restoring cached build plugins
5:13:35 PM: Attempting ruby version 2.7.1, read from environment
5:13:36 PM: Using ruby version 2.7.1
5:13:37 PM: Using PHP version 5.6
5:13:37 PM: 5.2 is already installed.
5:13:37 PM: Using Swift version 5.2
5:13:37 PM: Started restoring cached node modules
5:13:37 PM: Finished restoring cached node modules
5:13:37 PM: Installing NPM modules using NPM version 6.14.4
5:13:40 PM: npm WARN deprecated [email protected]: 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.
5:13:40 PM: npm WARN deprecated [email protected]: Deprecated. Please use https://github.com/webpack-contrib/mini-css-extract-plugin
5:13:42 PM: npm WARN deprecated [email protected]: This beta version is no longer supported. Please update to 1.1.0-beta.4
5:13:42 PM: npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
5:13:43 PM: npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
5:13:44 PM: npm WARN deprecated [email protected]: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
5:13:44 PM: npm WARN deprecated @hapi/[email protected]: joi is leaving the @hapi organization and moving back to 'joi' (https://github.com/sideway/joi/issues/2411)
5:13:48 PM: npm WARN deprecated [email protected]: this library is no longer supported
5:13:49 PM: npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
5:13:51 PM: npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
5:13:51 PM: npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
5:13:51 PM: npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
5:13:51 PM: npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
5:13:51 PM: npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
5:13:53 PM: npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
5:13:58 PM: npm WARN deprecated [email protected]: Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit <https://github.com/lukeed/kleur/releases/tag/v3.0.0\> for migration path(s).
5:13:58 PM: npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
5:13:59 PM: npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
5:13:59 PM: npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
5:14:00 PM: npm WARN deprecated [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
5:14:01 PM: npm WARN deprecated [email protected]: GraphQL Import has been deprecated and merged into GraphQL Tools, so it will no longer get updates. Use GraphQL Tools instead to stay up-to-date! Check out https://www.graphql-tools.com/docs/migration-from-import for migration and https://the-guild.dev/blog/graphql-tools-v6 for new changes.
5:14:03 PM: npm WARN deprecated [email protected]: 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.
5:14:03 PM: npm WARN deprecated @types/[email protected]: This is a stub types definition. vfile-message provides its own type definitions, so you do not need this installed.
5:14:05 PM: npm WARN deprecated [email protected]: use String.prototype.padStart()
5:14:05 PM: npm WARN deprecated [email protected]: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
5:14:05 PM: npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
5:14:05 PM: npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
5:15:27 PM: > [email protected] install /opt/build/repo/node_modules/inotify
5:15:27 PM: > node-gyp rebuild
5:15:28 PM: make: Entering directory '/opt/build/repo/node_modules/inotify/build'
5:15:28 PM: CXX(target) Release/obj.target/inotify/src/bindings.o
5:15:29 PM: In file included from ../src/bindings.cc:2:0:
5:15:29 PM: ../src/bindings.h:10:27: error: ‘Handle’ has not been declared
5:15:29 PM: static void Initialize(Handle<Object> target);
5:15:29 PM: ^
5:15:29 PM: ../src/bindings.h:10:33: error: expected ‘,’ or ‘...’ before ‘<’ token
5:15:29 PM: static void Initialize(Handle<Object> target);
5:15:29 PM: ^
5:15:29 PM: ../src/bindings.cc:11:27: error: variable or field ‘Initialize’ declared void
5:15:29 PM: void Inotify::Initialize(Handle<Object> exports) {
5:15:29 PM: ^
5:15:29 PM: ../src/bindings.cc:11:27: error: ‘Handle’ was not declared in this scope
5:15:29 PM: ../src/bindings.cc:11:40: error: expected primary-expression before ‘>’ token
5:15:29 PM: void Inotify::Initialize(Handle<Object> exports) {
5:15:29 PM: ^
5:15:29 PM: ../src/bindings.cc:11:42: error: ‘exports’ was not declared in this scope
5:15:29 PM: void Inotify::Initialize(Handle<Object> exports) {
5:15:29 PM: ^
5:15:29 PM: ../src/bindings.cc:313:1: error: expected ‘}’ at end of input
5:15:29 PM: }//namespace NodeInotify
5:15:29 PM: ^
5:15:29 PM: inotify.target.mk:112: recipe for target 'Release/obj.target/inotify/src/bindings.o' failed
5:15:29 PM: make: *** [Release/obj.target/inotify/src/bindings.o] Error 1
5:15:29 PM: make: Leaving directory '/opt/build/repo/node_modules/inotify/build'
5:15:29 PM: gyp ERR! build error
5:15:29 PM: gyp ERR! stack Error: `make` failed with exit code: 2
5:15:29 PM: gyp ERR! stack at ChildProcess.onExit (/opt/buildhome/.nvm/versions/node/v12.18.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
5:15:29 PM: gyp ERR! stack at ChildProcess.emit (events.js:315:20)
5:15:29 PM: gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
5:15:29 PM: gyp ERR! System Linux 4.19.112+
5:15:29 PM: gyp ERR! command "/opt/buildhome/.nvm/versions/node/v12.18.0/bin/node" "/opt/buildhome/.nvm/versions/node/v12.18.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
5:15:29 PM: gyp ERR! cwd /opt/build/repo/node_modules/inotify
5:15:29 PM: gyp ERR! node -v v12.18.0
5:15:29 PM: gyp ERR! node-gyp -v v5.1.0
5:15:29 PM: gyp ERR! not ok
5:15:33 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/babel-plugin-add-module-exports/node_modules/chokidar/node_modules/fsevents):
5:15:33 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
5:15:33 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents):
5:15:33 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
5:15:33 PM: npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":"<8.10.0"} (current: {"node":"12.18.0","npm":"6.14.4"})
5:15:33 PM: npm WARN notsup Not compatible with your version of node/npm: [email protected]
5:15:33 PM: npm WARN [email protected] requires a peer of webpack@^3.1.0 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of module-igniter@^1.1.0 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of netlify-cms@^2.0.0 | ^1.0.0 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN @pmmmwh/[email protected] requires a peer of react-refresh@^0.8.3 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of core-js@^3.0.0 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of ajv@^6.9.1 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of acorn@^6.0.0 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of @mdx-js/react@^1.0.0 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of immutable@^3.7.6 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of immutable@^3.7.6 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of immutable@^3.7.6 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of immutable@^3.7.6 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of immutable@^3.7.6 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of immutable@^3.7.6 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of immutable@^3.7.6 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of immutable@^3.7.6 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of netlify-cms-lib-widgets@^1.0.0 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of immutable@^3.7.6 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of immutable@^3.7.6 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of immutable@^3.7.6 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of netlify-cms-lib-widgets@^1.0.0 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of immutable@^3.7.6 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of immutable@>=3.6.2 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of seamless-immutable@^7.1.3 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of redux@^2.0.0 || ^3.0.0 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of immutable@>=3.8.1 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm WARN [email protected] requires a peer of immutable@>=3.8.1 but none is installed. You must install peer dependencies yourself.
5:15:33 PM: npm ERR! code ELIFECYCLE
5:15:33 PM: npm ERR! errno 1
5:15:33 PM: npm ERR! [email protected] install: `node-gyp rebuild`
5:15:33 PM: npm ERR! Exit status 1
5:15:33 PM: npm ERR!
5:15:33 PM: npm ERR! Failed at the [email protected] install script.
5:15:33 PM: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
5:15:33 PM: npm ERR! A complete log of this run can be found in:
5:15:33 PM: npm ERR! /opt/buildhome/.npm/_logs/2020-09-25T15_15_33_101Z-debug.log
5:15:33 PM: Error during NPM install
5:15:33 PM: Error running command: Build script returned non-zero exit code: 1
5:15:33 PM: Failing build: Failed to build site
5:15:33 PM: Failed during stage 'building site': Build script returned non-zero exit code: 1
5:15:33 PM: Finished processing build request in 2m6.073876389s |
node-gyp is a PITA.
entrypoint.sh
|
Not sure if it's related to #67 but here's the log:
The text was updated successfully, but these errors were encountered: