I've been deploying normally but last deploy is showing me this:
1:58:34 PM: build-image version: 4c0c1cadee6a31c9bb8d824514030009c4c05c6a (focal)
1:58:34 PM: build-image tag: v4.15.0
1:58:34 PM: buildbot version: 44377b3b6a4027dd8a09c3df7d29646ce9192423
1:58:34 PM: Fetching cached dependencies
1:58:34 PM: Starting to download cache of 419.1MB
1:58:38 PM: Finished downloading cache in 4.318992901s
1:58:38 PM: Starting to extract cache
1:58:48 PM: Finished extracting cache in 9.085548565s
1:58:48 PM: Finished fetching cache in 13.475179533s
1:58:48 PM: Starting to prepare the repo for build
1:58:48 PM: Preparing Git Reference refs/heads/main
1:58:51 PM: Parsing package.json dependencies
1:58:52 PM: Section completed: initializing
1:58:52 PM: Starting build script
1:58:52 PM: Installing dependencies
1:58:52 PM: Python version set to 2.7
1:58:52 PM: Started restoring cached node version
1:58:53 PM: Finished restoring cached node version
1:58:53 PM: v16.18.1 is already installed.
1:58:53 PM: Now using node v16.18.1 (npm v8.19.2)
1:58:54 PM: Enabling node corepack
1:58:54 PM: Started restoring cached build plugins
1:58:54 PM: Finished restoring cached build plugins
1:58:54 PM: Attempting ruby version 2.7.2, read from environment
1:58:54 PM: Using ruby version 2.7.2
1:58:55 PM: Using PHP version 8.0
1:58:55 PM: Started restoring cached yarn cache
1:59:00 PM: Finished restoring cached yarn cache
1:59:00 PM: No yarn workspaces detected
1:59:00 PM: Started restoring cached node modules
1:59:00 PM: Finished restoring cached node modules
1:59:01 PM: Installing NPM modules using Yarn version 1.22.19
1:59:01 PM: yarn install v1.22.19
1:59:01 PM: warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
1:59:01 PM: [1/4] Resolving packages...
1:59:12 PM: [2/4] Fetching packages...
1:59:14 PM: [3/4] Linking dependencies...
1:59:14 PM: warning "#ckeditor/ckeditor5-dev-utils > ts-loader#9.4.1" has unmet peer dependency "typescript#*".
1:59:14 PM: warning "#ckeditor/ckeditor5-dev-utils > ts-loader#9.4.1" has incorrect peer dependency "webpack#^5.0.0".
1:59:14 PM: warning " > bootstrap#4.6.1" has unmet peer dependency "popper.js#^1.16.1".
1:59:14 PM: warning " > v-calendar#2.4.1" has unmet peer dependency "#popperjs/core#^2.4.0".
1:59:14 PM: warning " > vue-cropperjs#5.0.0" has incorrect peer dependency "vue#>=3.0.0".
1:59:14 PM: warning " > vue-instantsearch#4.3.3" has unmet peer dependency "algoliasearch#>= 3.32.0 < 5".
1:59:14 PM: warning "vue-instantsearch > instantsearch.js#4.40.4" has unmet peer dependency "algoliasearch#>= 3.1 < 5".
1:59:14 PM: warning "vue-instantsearch > instantsearch.js > algoliasearch-helper#3.8.2" has unmet peer dependency "algoliasearch#>= 3.1 < 5".
1:59:14 PM: warning " > #vue/cli-plugin-eslint#4.5.17" has incorrect peer dependency "eslint#>= 1.6.0 < 7.0.0".
1:59:14 PM: warning "#vue/cli-plugin-eslint > eslint-loader#2.2.1" has incorrect peer dependency "eslint#>=1.6.0 <7.0.0".
1:59:14 PM: warning " > vue-loader#15.9.8" has unmet peer dependency "css-loader#*".
1:59:14 PM: warning " > #vue/eslint-config-prettier#6.0.0" has unmet peer dependency "eslint-plugin-prettier#^3.1.0".
1:59:14 PM: warning " > #vue/eslint-config-prettier#6.0.0" has unmet peer dependency "prettier#>= 1.13.0".
1:59:14 PM: warning " > eslint-plugin-vue#6.2.2" has incorrect peer dependency "eslint#^5.0.0 || ^6.0.0".
1:59:18 PM: [4/4] Building fresh packages...
1:59:18 PM: success Saved lockfile.
1:59:18 PM: Done in 17.36s.
1:59:18 PM: NPM modules installed using Yarn
1:59:18 PM: Started restoring cached go cache
1:59:18 PM: Finished restoring cached go cache
1:59:18 PM: Installing Go version 1.17 (requested 1.17)
1:59:23 PM: unset GOOS;
1:59:23 PM: unset GOARCH;
1:59:23 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.17.linux.amd64';
1:59:23 PM: export PATH="/opt/buildhome/.gimme/versions/go1.17.linux.amd64/bin:${PATH}";
1:59:23 PM: go version >&2;
1:59:23 PM: export GIMME_ENV="/opt/buildhome/.gimme/env/go1.17.linux.amd64.env"
1:59:23 PM: go version go1.17 linux/amd64
1:59:23 PM: Detected 1 framework(s)
1:59:23 PM: "vue" at version "4.5.17"
1:59:23 PM: Installing missing commands
1:59:23 PM: Verify run directory
1:59:25 PM: ────────────────────────────────────────────────────────────────
1:59:25 PM: 1. Build command from Netlify app
1:59:25 PM: ────────────────────────────────────────────────────────────────
1:59:25 PM:
1:59:25 PM: $ npm run build
1:59:25 PM: > oceanly#1.0.0 build
1:59:25 PM: > vue-cli-service build
1:59:26 PM: Browserslist: caniuse-lite is outdated. Please run:
1:59:26 PM: npx browserslist#latest --update-db
1:59:26 PM: Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
1:59:26 PM: - Building for production...
1:59:27 PM: ERROR TypeError: Cannot read properties of undefined (reading 'version')
1:59:27 PM: TypeError: Cannot read properties of undefined (reading 'version')
1:59:27 PM: at getCompilationHooks (/opt/build/repo/node_modules/#ckeditor/ckeditor5-dev-webpack-plugin/lib/servetranslations.js:206:29)
1:59:27 PM: at /opt/build/repo/node_modules/#ckeditor/ckeditor5-dev-webpack-plugin/lib/servetranslations.js:95:3
1:59:27 PM: at SyncHook.eval [as call] (eval at create (/opt/build/repo/node_modules/tapable/lib/HookCodeFactory.js:19:10), <anonymous>:21:1)
1:59:27 PM: at SyncHook.lazyCompileHook (/opt/build/repo/node_modules/tapable/lib/Hook.js:154:20)
1:59:27 PM: at Compiler.newCompilation (/opt/build/repo/node_modules/webpack/lib/Compiler.js:631:26)
1:59:27 PM: at /opt/build/repo/node_modules/webpack/lib/Compiler.js:667:29
1:59:27 PM: at AsyncSeriesHook.eval [as callAsync] (eval at create (/opt/build/repo/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
1:59:27 PM: at AsyncSeriesHook.lazyCompileHook (/opt/build/repo/node_modules/tapable/lib/Hook.js:154:20)
1:59:27 PM: at Compiler.compile (/opt/build/repo/node_modules/webpack/lib/Compiler.js:662:28)
1:59:27 PM: at /opt/build/repo/node_modules/webpack/lib/Compiler.js:321:11
1:59:27 PM: at Compiler.readRecords (/opt/build/repo/node_modules/webpack/lib/Compiler.js:529:11)
1:59:27 PM: at /opt/build/repo/node_modules/webpack/lib/Compiler.js:318:10
1:59:27 PM: at AsyncSeriesHook.eval [as callAsync] (eval at create (/opt/build/repo/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
1:59:27 PM: at AsyncSeriesHook.lazyCompileHook (/opt/build/repo/node_modules/tapable/lib/Hook.js:154:20)
1:59:27 PM: at /opt/build/repo/node_modules/webpack/lib/Compiler.js:315:19
1:59:27 PM: at AsyncSeriesHook.eval [as callAsync] (eval at create (/opt/build/repo/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:15:1)
1:59:27 PM:
1:59:27 PM: ────────────────────────────────────────────────────────────────
1:59:27 PM: "build.command" failed
1:59:27 PM: ────────────────────────────────────────────────────────────────
I can not understand which 'version' is referenced here.
I have been searching about this error. I compared with my previous good deploy 3 days ago..
the difference is related with these lines:
ERROR TypeError: Cannot read properties of undefined (reading 'version')
1:59:27 PM: TypeError: Cannot read properties of undefined (reading 'version')
1:59:27 PM: at getCompilationHooks (/opt/build/repo/node_modules/#ckeditor/ckeditor5-dev-webpack-plugin/lib/servetranslations.js:206:29)
I was thinking was related with webpack, so I executed this:
npm list webpack
then I save it in package.json with:
npm install --save-dev "webpack#4.46.0"
All is working in my dev environment, but when I deploy with Netlify it is generating the error.
The previous versions of CKEditor 31.1.x had issues with webpack v4.46.0. I tried to update to webpack v5 but the error persisted. So I searched in the official documentation of the pluggin, and I found last releases solving problems with CKEditor and webpack. I reported the issue to the development team in GitHub and they solved it.
The solution was wait until the new release (v31.1.11) and install it.
Run these lines to get last version of the plugins:
npm i #ckeditor/ckeditor5-dev-utils
npm i #ckeditor/ckeditor5-dev-webpack-plugin
In case you are using more pluggins of CKEditor run the others pluggins detailed in the release
#ckeditor/ckeditor5-dev-docs: v31.1.11 => v31.1.12
#ckeditor/ckeditor5-dev-env: v31.1.11 => v31.1.12
#ckeditor/ckeditor5-dev-tests: v31.1.11 => v31.1.12
#ckeditor/ckeditor5-dev-utils: v31.1.11 => v31.1.12
#ckeditor/ckeditor5-dev-webpack-plugin: v31.1.11 => v31.1.12
#ckeditor/jsdoc-plugins: v31.1.11 => v31.1.12
Oficial documentation: https://github.com/ckeditor/ckeditor5-dev
Issue reported: https://github.com/ckeditor/ckeditor5/issues/12887
Change log: https://github.com/ckeditor/ckeditor5-dev/blob/master/CHANGELOG.md
Especial thanks to pomek
Related
I am trying to deploy a really simple Go function on Netlify functions.
I followed the guide, but the guide does not explain the Go setup very well.
I used the currently recommended way to do it, with basically go init, changing my go file as needed, then go mod tidy. This creates the appropriate go.mod and go.sum files and I can build locally.
I also created a very simple website on website/index.html so I can test the site can "run" the function. That means I configured my "base directory" for Netlify to build as website/ (which is how I normally do with other websites I have on Netlify, and this works fine).
EDIT: I tried moving everything to the root dir instead of using website/ as the base dir, but the problem remain the same.
I then moved all the Go files, including go.mod and go.sum, to website/netlify/functions/analytics/ (so my function will be called analytics as explained in the guide) and pushed.
Contents of website/netlify/functions/analytics:
go.mod go.sum handlers.go main.go main_test.go
However, the Netlify build fails with:
5:33:45 PM: ❯ Current directory
5:33:45 PM: /opt/build/repo/website
5:33:45 PM:
5:33:45 PM: ❯ Config file
5:33:45 PM: No config file was defined: using default values.
5:33:45 PM:
5:33:45 PM: ❯ Context
5:33:45 PM: production
5:33:45 PM:
5:33:45 PM: ────────────────────────────────────────────────────────────────
5:33:45 PM: 1. Functions bundling
5:33:45 PM: ────────────────────────────────────────────────────────────────
5:33:45 PM:
5:33:45 PM: Packaging Functions from netlify/functions directory:
5:33:45 PM: - analytics/main.go
5:33:45 PM:
5:33:45 PM: Could not compile Go function analytics:
5:33:45 PM:
5:33:45 PM: ────────────────────────────────────────────────────────────────
5:33:45 PM: Bundling of Function "analytics" failed
5:33:45 PM: ────────────────────────────────────────────────────────────────
5:33:45 PM:
5:33:45 PM: Error message
5:33:45 PM: Command failed with exit code 1: go build -o /tmp/zisi-629b7b4be8f858000804bf6c/analytics -ldflags -s -w (https://ntl.fyi/exit-code-1)
5:33:45 PM: go: github.com/aws/aws-lambda-go#v1.32.0 requires
5:33:45 PM: github.com/stretchr/testify#v1.6.1: missing go.sum entry; to add it:
5:33:45 PM: go mod download github.com/stretchr/testify
5:33:45 PM:
5:33:45 PM: Error location
5:33:45 PM: While bundling Function "analytics"
5:33:45 PM:
5:33:45 PM: Resolved config
5:33:45 PM: build:
5:33:45 PM: base: /opt/build/repo/website
5:33:45 PM: publish: /opt/build/repo/website
5:33:45 PM: publishOrigin: ui
5:33:45 PM: functionsDirectory: /opt/build/repo/website/netlify/functions
The error shows that Netlify can find the go files correctly, but it for some reason seems to ignore go.sum because that file contains the correct checksums:
github.com/aws/aws-lambda-go v1.32.0 h1:i8MflawW1hoyYp85GMH7LhvAs4cqzL7LOS6fSv8l2KM=
github.com/aws/aws-lambda-go v1.32.0/go.mod h1:IF5Q7wj4VyZyUFnZ54IQqeWtctHQ9tz+KhcbDenr220=
github.com/davecgh/go-spew v1.1.1 h1:vj9j/u1bqnvCEfJOwUhtlOARqs3+rkHYY13jYWTU97c=
github.com/pmezard/go-difflib v1.0.0 h1:4DBwDE0NGyQoBHbLQYPwSUPoCMWR5BEzIk/f1lZbAQM=
github.com/stretchr/testify v1.6.1 h1:hDPOHmpOpP40lSULcqw7IrRb/u7w6RpDC9399XyoNd0=
gopkg.in/yaml.v3 v3.0.0-20200615113413-eeeca48fe776 h1:tQIYjPdBoyREyB9XMu+nnTclpTYkz2zFM+lzLJFO4gQ=
What could be wrong and how can I fix that?
As of writing, Netlify is using an older version of Go, 1.16.5, to build.
This means my go.mod file shouldn't even have been accepted by the older Go compiler! Anyway, I installed that version of Go locally to try it out...
Here's how to install a specific version of Go (assuming you have go 1.18 installed locally):
$ go install golang.org/dl/go1.16.5#latest
$ go1.16.5 download
Now you can run go1.16.5 to try out the older compiler.
I wrote a Makefile that lets me use whatever version of Go to build... looks like this:
## To use a different version of Go, run like this:
## make all GO=go1.16.5
GO:=go
.PHONY: test
test:
cd analytics && $(GO) test .
../netlify/functions/analytics: test
cd analytics && $(GO) build -o ../netlify/functions/analytics .
all: ../netlify/functions/analytics
And here's the result using go1.16.5:
▶ make all GO=go1.16.5
cd analytics && go1.16.5 test .
go: github.com/aws/aws-lambda-go#v1.32.0 requires
github.com/stretchr/testify#v1.6.1: missing go.sum entry; to add it:
go mod download github.com/stretchr/testify
make: *** [test] Error 1
That's the same error I see on Netlify! Cool, so that's the problem.
Now, to fix the problem I had to remove go.mod and go.sum and re-generate them using the older Go version, which I did by writing this Make task:
.PHONY: setup
setup:
cd analytics && rm go.mod go.sum && $(GO) mod init renato/analytics && $(GO) mod tidy
Now, the builds succeeds locally with the older Go:
▶ make setup all GO=go1.16.5
cd analytics && rm go.mod go.sum && go1.16.5 mod init renato/analytics && go1.16.5 mod tidy
go: creating new go.mod: module renato/analytics
go: to add module requirements and sums:
go mod tidy
go: finding module for package github.com/aws/aws-lambda-go/lambda
go: finding module for package github.com/aws/aws-lambda-go/events
go: found github.com/aws/aws-lambda-go/events in github.com/aws/aws-lambda-go v1.32.0
go: found github.com/aws/aws-lambda-go/lambda in github.com/aws/aws-lambda-go v1.32.0
cd analytics && go1.16.5 test .
ok renato/analytics 0.166s
cd analytics && go1.16.5 build -o ../netlify/functions/analytics .
I decided to commit the Go files after this to let Netlify see the right versions of these files, but I also "customized the build" (as explained in the docs) by just telling Netlify to run my build command, make all (no make setup as it's not needed if you commit the go.mod and go.sum files) on the Netlify UI (in the site settings). This is probably not necessary but I wanted to be certain the right commands are being executed.
And finally, the build works on Netlify as well!!
7:36:59 PM: ────────────────────────────────────────────────────────────────
7:36:59 PM: 1. Build command from Netlify app
7:36:59 PM: ────────────────────────────────────────────────────────────────
7:36:59 PM:
7:36:59 PM: $ make all
7:36:59 PM: cd analytics && go test .
7:37:00 PM: go: downloading github.com/aws/aws-lambda-go v1.32.0
7:37:08 PM: ok renato/analytics 0.017s
7:37:08 PM: cd analytics && go build -o ../netlify/functions/analytics .
7:37:09 PM:
7:37:09 PM: (build.command completed in 9.2s)
7:37:09 PM:
7:37:09 PM: ────────────────────────────────────────────────────────────────
7:37:09 PM: 2. Functions bundling
7:37:09 PM: ────────────────────────────────────────────────────────────────
7:37:09 PM:
7:37:09 PM: Packaging Functions from netlify/functions directory:
7:37:09 PM: - analytics
7:37:09 PM:
7:37:09 PM:
7:37:09 PM: (Functions bundling completed in 101ms)
So, the problem was the Go version Netlify is outdated, and unfortunately Go has been messing around with the Go mod format which is causing compatibility issues like this... you may need the exact version of the Go compiler to get a given project to compile properly, as in this case.
When I tried to install near-sdk-as on my laptop (Intel-based macOS 10.13) with the command:
yarn add -D near-sdk-as
I got the following error:
❯ yarn add -D near-sdk-as
yarn add v1.22.17
info No lockfile found.
[1/4] 🔍 Resolving packages...
warning near-sdk-as > near-sdk-core > near-vm > binary-install > axios#0.19.2: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
[2/4] 🚚 Fetching packages...
[3/4] 🔗 Linking dependencies...
warning "near-sdk-as > near-sdk-core > #as-pect/cli#6.2.4" has incorrect peer dependency "assemblyscript#^0.19.3".
warning "near-sdk-as > near-sdk-core > #as-pect/cli > #as-pect/assembly#6.2.0" has incorrect peer dependency "assemblyscript#^0.19.3".
warning "near-sdk-as > near-sdk-core > #as-pect/cli > #as-pect/core#6.2.1" has incorrect peer dependency "assemblyscript#^0.19.3".
[4/4] 🔨 Building fresh packages...
error /Users/admin/Develop/Learn-Near/NEAR-101/node_modules/near-vm: Command failed.
Exit code: 1
Command: node ./install.js
Arguments:
Directory: /Users/admin/Develop/Learn-Near/NEAR-101/node_modules/near-vm
Output:
/Users/admin/Develop/Learn-Near/NEAR-101/node_modules/follow-redirects/node_modules/debug/src/debug.js:47
hash = ((hash <
SyntaxError: Unexpected end of input
at Object.compileFunction (node:vm:352:18)
at wrapSafe (node:internal/modules/cjs/loader:1032:15)
at Module._compile (node:internal/modules/cjs/loader:1067:27)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1155:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Module.require (node:internal/modules/cjs/loader:1005:19)
at require (node:internal/modules/cjs/helpers:102:18)
at Object.<anonymous> (/Users/admin/Develop/Learn-Near/NEAR-101/node_modules/follow-redirects/node_modules/debug/src/node.js:14:28)
at Module._compile (node:internal/modules/cjs/loader:1103:14)
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
Other info:
npm version: 8.3.1
yarn version: v1.22.17
Any thoughts on how to fix the error and complete the sdk installation?
Thanks!
Try yarn cache clean --force first, then rerun yarn.
Why? You have broken dependency files cached, so you want to clean the cache and download from scratch
I try to install Plotly extension to Jupiterlab. After I installed every package (Anaconda, jupyterlab "ipywidgets>=7.5") I try to install "jupyter labextension install jupyterlab-plotly#4.14.3" but I got an error message: RuntimeError: JupyterLab failed to build
I try to identify the problem from the Log file, but I have no idea what to do next
The log file:
Yarn configuration loaded.
Node v15.12.0
"C:\Users\Szarka Roland\anaconda3\npm.CMD" pack jupyterlab-plotly#4.14.3
npm notice
npm notice package: jupyterlab-plotly#4.14.3
npm notice === Tarball Contents ===
npm notice 156B README.md
npm notice 6.3kB dist/javascript-renderer-extension.js
npm notice 1.0kB package.json
npm notice 545B style/index.css
npm notice 1.0kB style/plotly.svg
npm notice === Tarball Details ===
npm notice name: jupyterlab-plotly
npm notice version: 4.14.3
npm notice filename: jupyterlab-plotly-4.14.3.tgz
npm notice package size: 3.1 kB
npm notice unpacked size: 9.1 kB
npm notice shasum: bb424a50226c2ce1b816f061a8123f0f42418fc0
npm notice integrity: sha512-6ZdmIQ5fDiBTY[...]nASwRNCf1U1Cg==
npm notice total files: 5
npm notice
jupyterlab-plotly-4.14.3.tgz
Yarn configuration loaded.
Node v15.12.0
Building jupyterlab assets (build:prod:minimize)
> node "C:\Users\Szarka Roland\anaconda3\lib\site-packages\jupyterlab\staging\yarn.js" install --non-interactive
yarn install v1.15.2
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
info fsevents#1.2.11: The platform "win32" is incompatible with this module.
info "fsevents#1.2.11" is an optional dependency and failed compatibility check. Excluding it from installation.
[4/5] Linking dependencies...
warning "jupyterlab-plotly > #lumino/widgets > #lumino/coreutils#1.5.3" has unmet peer dependency "crypto#1.0.1".
[5/5] Building fresh packages...
success Saved lockfile.
Done in 9.81s.
> node "C:\Users\Szarka Roland\anaconda3\lib\site-packages\jupyterlab\staging\yarn.js" yarn-deduplicate -s fewer
yarn run v1.15.2
error Command "yarn-deduplicate" not found.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
> node "C:\Users\Szarka Roland\anaconda3\lib\site-packages\jupyterlab\staging\yarn.js"
yarn install v1.15.2
[1/5] Validating package.json...
[2/5] Resolving packages...
success Already up-to-date.
Done in 0.52s.
> node "C:\Users\Szarka Roland\anaconda3\lib\site-packages\jupyterlab\staging\yarn.js" run build:prod:minimize
yarn run v1.15.2
$ ensure-max-old-space webpack --config webpack.prod.minimize.config.js
node:internal/modules/cjs/loader:352
throw err;
^
Error: Cannot find module 'C:\Users\Szarka Roland\anaconda3\share\jupyter\lab\staging\node_modules\which\which.js'. Please verify that the package.json has a valid "main" entry
at tryPackage (node:internal/modules/cjs/loader:344:19)
at Function.Module._findPath (node:internal/modules/cjs/loader:557:18)
at Function.Module._resolveFilename (node:internal/modules/cjs/loader:910:27)
at Function.Module._load (node:internal/modules/cjs/loader:769:27)
at Module.require (node:internal/modules/cjs/loader:996:19)
at require (node:internal/modules/cjs/helpers:92:18)
at Object.<anonymous> (C:\Users\Szarka Roland\anaconda3\share\jupyter\lab\staging\node_modules\#jupyterlab\buildutils\lib\ensure-max-old-space.js:28:28)
at Module._compile (node:internal/modules/cjs/loader:1092:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1121:10)
at Module.load (node:internal/modules/cjs/loader:972:32) {
code: 'MODULE_NOT_FOUND',
path: 'C:\\Users\\Szarka Roland\\anaconda3\\share\\jupyter\\lab\\staging\\node_modules\\which\\package.json',
requestPath: 'which'
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
JupyterLab failed to build
Traceback (most recent call last):
File "C:\Users\Szarka Roland\anaconda3\lib\site-packages\jupyterlab\debuglog.py", line 47, in debug_logging
yield
File "C:\Users\Szarka Roland\anaconda3\lib\site-packages\jupyterlab\labextensions.py", line 105, in start
command=command, app_options=app_options)
File "C:\Users\Szarka Roland\anaconda3\lib\site-packages\jupyterlab\commands.py", line 459, in build
command=command, clean_staging=clean_staging)
File "C:\Users\Szarka Roland\anaconda3\lib\site-packages\jupyterlab\commands.py", line 669, in build
raise RuntimeError(msg)
RuntimeError: JupyterLab failed to build
Exiting application: jupyter
System:
OS: macOS Mojave 10.14.5
CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU # 2.30GHz
Memory: 50.37 MB / 8.00 GB
Shell: 5.3 - /bin/zsh
Binaries:
Node: 12.13.0 - ~/.nvm/versions/node/v12.13.0/bin/node
Yarn: 1.19.1 - /usr/local/bin/yarn
npm: 6.12.0 - ~/.nvm/versions/node/v12.13.0/bin/npm
npmPackages:
babel-plugin-styled-components: ^1.10.6 => 1.10.6
styled-components: ^5.0.0-rc.1 => 5.0.0-rc.1
Why I am getting this warning, even though I can see packages in node_modules
yarn add eslint-config-airbnb
yarn add v1.19.1
[1/4] 🔍 Resolving packages...
[2/4] 🚚 Fetching packages...
[3/4] 🔗 Linking dependencies...
warning "eslint-config-airbnb > eslint-config-airbnb-base#14.0.0" has unmet peer dependency "eslint-plugin-import#^2.18.2".
warning " > eslint-config-airbnb#18.0.1" has unmet peer dependency "eslint-plugin-import#^2.18.2".
warning " > eslint-config-airbnb#18.0.1" has unmet peer dependency "eslint-plugin-jsx-a11y#^6.2.3".
warning " > eslint-config-airbnb#18.0.1" has incorrect peer dependency "eslint-plugin-react-hooks#^1.7.0".
[4/4] 🔨 Building fresh packages...
success Saved lockfile.
success Saved 3 new dependencies.
info Direct dependencies
└─ eslint-config-airbnb#18.0.1
info All dependencies
├─ confusing-browser-globals#1.0.9
├─ eslint-config-airbnb-base#14.0.0
└─ eslint-config-airbnb#18.0.1
✨ Done in 3.24s.
yarn add styled-components#beta
yarn add v1.19.1
[1/4] 🔍 Resolving packages...
[2/4] 🚚 Fetching packages...
[3/4] 🔗 Linking dependencies...
warning "styled-components > stylis-rule-sheet#0.0.10" has unmet peer dependency "stylis#^3.5.0".
warning " > styled-components#5.0.0-rc.1" has unmet peer dependency "react-is#>= 16.8.0".
[4/4] 🔨 Building fresh packages...
success Saved 1 new dependency.
info Direct dependencies
└─ styled-components#5.0.0-rc.1
info All dependencies
└─ styled-components#5.0.0-rc.1
✨ Done in 3.19s.
I've added a couple of blogposts to my blogdown/netlify backed site today:
https://github.com/brainstorm/brainblog/blob/master/content/brainstorm/2018-03-12-umccr-arteria.md
https://github.com/brainstorm/brainblog/blob/master/content/brainstorm/2018-03-13-umccr-pcgr.md
And while they render/preview successfully on R-Studio:
Those two blogposts do not show up on Netlify-hosted site after pushing/deploying (see deploy log below). *Even a manual deploy triggering (with clear cache checkbox on), fails to update the index page accordingly to show the two new posts:
From Netlify's side, this is a successful deployment, along with all previous pushes from github, as far as I can see from their web console:
4:17:37 PM: Build ready to start
4:17:39 PM: Fetching cached dependencies
4:17:39 PM: Starting to download cache of 65.2MB
4:17:39 PM: Finished downloading cache in 625.456927ms
4:17:39 PM: Starting to extract cache
4:17:40 PM: Finished extracting cache in 1.126872353s
4:17:41 PM: Finished fetching cache in 1.869794305s
4:17:41 PM: Starting to prepare the repo for build
4:17:41 PM: Preparing Git Reference refs/heads/master
4:17:42 PM: Found netlify.toml. Overriding site configuration
4:17:42 PM: Different build command detected, going to use the one specified in the toml file: 'HUGO_BASEURL='https://blogs.nopcode.org/brainstorm' hugo' versus 'hugo' in the site
4:17:42 PM: Starting build script
4:17:42 PM: Installing dependencies
4:17:43 PM: Started restoring cached node version
4:17:45 PM: Finished restoring cached node version
4:17:46 PM: v8.10.0 is already installed.
4:17:47 PM: Now using node v8.10.0 (npm v5.6.0)
4:17:47 PM: Attempting ruby version 2.4.3, read from .ruby-version file
4:17:48 PM: Using ruby version 2.4.3
4:17:48 PM: Using PHP version 5.6
4:17:48 PM: Installing Hugo 0.37.1
4:17:50 PM: Installing missing commands
4:17:50 PM: Executing user command: HUGO_BASEURL='https://blogs.nopcode.org/brainstorm' hugo
4:17:50 PM: Building sites …
4:17:50 PM:
4:17:50 PM: | EN
4:17:50 PM: +------------------+-----+
4:17:50 PM: Pages | 221
4:17:50 PM: Paginator pages | 0
4:17:51 PM: Non-page files | 0
4:17:51 PM: Static files | 45
4:17:51 PM: Processed images | 0
4:17:51 PM: Aliases | 0
4:17:51 PM: Sitemaps | 1
4:17:51 PM: Cleaned | 0
4:17:51 PM: Total in 283 ms
4:17:51 PM: Caching artifacts
4:17:51 PM: Started saving pip cache
4:17:51 PM: Finished saving pip cache
4:17:51 PM: Started saving emacs cask dependencies
4:17:51 PM: Finished saving emacs cask dependencies
4:17:51 PM: Started saving maven dependencies
4:17:51 PM: Finished saving maven dependencies
4:17:51 PM: Started saving boot dependencies
4:17:51 PM: Finished saving boot dependencies
4:17:51 PM: Build script success
4:17:51 PM: Starting to deploy site from 'public'
4:17:58 PM: Starting post processing
4:18:07 PM: Finished processing build request in 28.354802492s
4:18:12 PM: Post processing done
4:18:12 PM: Site is live
On Netlify's defense, this could be a symptom of baseUrl issues not being fully solved yet, as I pointed out in an earlier question... any hints very welcome.
Apparently after re-triggering a deploy today, one of the posts showed up, which leads me to believe that this is a timezone difference issue.
A consequence of Australia living in the future compared with the rest of the world X"D
The missing posts are due to the date of your front-matter being in the future.
Note: The build will use the Netlify build server's time.
Today's date is 2018-03-12
date: '2018-03-13T16:00:00.000000+00:00'
Run the Hugo command hugo server --buildFuture to see which posts will build on later deploys.
Just leaving this answer here in case anyone else is as dumb as me... if you can see the post in Rstudio but not on netlifies, make sure that draft:no in your yaml.