I'm trying to upgrade docusaurus to the latest version v2.3.1 but got the following errors when running yarn start
yarn start
yarn run v1.22.19
$ docusaurus start
[INFO] Starting the development server...
[ERROR] ValidationError: "trackingID" is required
[INFO] Docusaurus version: 2.3.1
Node version: v18.12.1
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Here is the config:
https://github.com/OpenAPITools/openapi-generator/blob/relesae-fix/website/docusaurus.config.js
Searched for the error message but got nothing related to trackingID in particular.
Related
I'm trying to use cypress 8.4.0. Used 'npm install cypress --save-dev' to install it. However, after installation, running any command
npx cypress open/ run end up with error.
It looks like this is your first time using Cypress: 8.4.0
Cypress failed to start.
This may be due to a missing library or dependency. https://on.cypress.io/required-dependencies
Please refer to the error below for more details.
----------
Command failed with exit code 2147483651: C:\Users\NEX20UR\AppData\Local\Cypress\Cache\8.4.0\Cypress\Cypress.exe --smoke-test --ping=672
----------
When I run 'npx cypress verify', I got below error:
Cypress verification timed out.
This command failed with the following output:
C:\Users\NEX20UR\AppData\Local\Cypress\Cache\8.4.0\Cypress\Cypress.exe --smoke-test --ping=466
----------
Command timed out after 30000 milliseconds: C:\Users\NEX20UR\AppData\Local\Cypress\Cache\8.4.0\Cypress\Cypress.exe --smoke-test --ping=466
Timed out
more details:
Cypress package version: 8.4.0
Cypress binary version: 8.4.0
Electron version: 13.2.0
Bundled Node version:
14.16.0
PS: I uninstalled and installed many times.
Remove cache from location mentioned below:
C:\Users\username\AppData\Local\Cypress
then reinstall cypress
npm install --save-dev cypress#8.4.0 -force,
I am trying to debug my react-native app using 'Debug in Exponent'
and I got this error where the packager is starting successfully but with the error in the console
Configurations are:
VSCODE Version: 1.35.1
React-Native VS Code extension version: 0.10.2
Node.js: 10.2.0
OS: Linux x64 4.4.0-154-generic
Expo: 2.21.1
I have tried upgrading and downgrading the vscode.
deleted the node_module and installed npm again.
I even cleared out all the settings and created the fresh launch.json in .vscode so far with no success
error in console is as follows
[Info] Making sure your project uses the correct dependencies for Expo. This may take a while...
Checking if this is Expo app......
[Info] Packager is already running.
[Info] Prewarming bundle cache. This may take a while ...
[Info] Building and running application.
[Error] TypeError: Cannot read property 'getCurrentUserAsync' of undefined
Same problem occurs with the configuration below :
VSCODE Version: 1.36.1
React-Native VS Code extension version: 0.10.2
Node.js: 10.15.1
OS: Win32 x64
Expo: 3.0.2
The temporary workaround is described here which worked for me..
We use Artifactory Pro.
We have a virtual repo in which we've stored the installer of yarn 23.04.
On another instance we have running a Jenkins 1 server. We have some maven project and our maven goal is to perform:
clean source:jar install -DskipTests -Pyarn -X
We use the profile yarn so a yarn install will be executed.
We are not using any proxy about our configuration. We have turned them off explicitly
Most of the time the jenkins job works:
[INFO] yarn install v0.23.4
[INFO] [1/4] Resolving packages...
[INFO] [2/4] Fetching packages...
[ERROR] warning fsevents#1.1.1: The platform "linux" is incompatible with this module.
[INFO] info "fsevents#1.1.1" is an optional dependency and failed compatibility check. Excluding it from installation.
[INFO] [3/4] Linking dependencies...
[ERROR] warning "ng2-translate#5.0.0" has incorrect peer dependency "#angular/core#^2.0.0".
[ERROR] warning "ng2-translate#5.0.0" has incorrect peer dependency "#angular/http#^2.0.0".
[ERROR] warning "sass-loader#6.0.5" has incorrect peer dependency "webpack#^2.0.0".
[INFO] [4/4] Building fresh packages...
[INFO] success Saved lockfile.
But on certain occasions it fails:
[INFO] yarn install v0.23.4
[INFO] [1/4] Resolving packages...
[ERROR] an unexpected error occurred: "http://xxx/artifactory/api/npm/npm/xxx: Request\ "http://xxx/artifactory/api/npm/npm/xxx" returned a 403
The yarn is in our artifactory. So we think the only issue can be a 'bad connection' between jenkins and Artifactory or the apache which is running above Artifactory.
Is there some specific setting in Apache that could cause this behaviour of Artifactory?
I am learning ionic2. I thought the sample app was a good starting point but unfortunately, I can't get it work. It complained about missing module.Please see the output:
lola#ubuntu:~/pj/ionic-conference-app$ ionic serve
Running 'serve:before' gulp task before serve
[08:53:57] Starting 'sass'...
[08:53:57] Starting 'html'...
[08:53:57] Starting 'fonts'...
[08:53:57] Starting 'scripts'...
[08:53:57] Finished 'scripts' after 63 ms
[08:53:57] Finished 'html' after 115 ms
[08:53:57] Finished 'fonts' after 114 ms
[08:53:58] Finished 'sass' after 888 ms
[08:53:58] Starting 'watch'...
✗ Caught exception:
Error: Cannot find module 'babelify' from '/home/lola/pj/ionic-conference-app'
at /home/lola/pj/ionic-conference-app/node_modules/ionic-gulp-browserify-es2015/node_modules/browserify/node_modules/resolve/lib/async.js:46:17
at process (/home/lola/pj/ionic-conference-app/node_modules/ionic-gulp-browserify-es2015/node_modules/browserify/node_modules/resolve/lib/async.js:173:43)
at ondir (/home/lola/pj/ionic-conference-app/node_modules/ionic-gulp-browserify-es2015/node_modules/browserify/node_modules/resolve/lib/async.js:188:17)
at load (/home/lola/pj/ionic-conference-app/node_modules/ionic-gulp-browserify-es2015/node_modules/browserify/node_modules/resolve/lib/async.js:69:43)
at onex (/home/lola/pj/ionic-conference-app/node_modules/ionic-gulp-browserify-es2015/node_modules/browserify/node_modules/resolve/lib/async.js:92:31)
at /home/lola/pj/ionic-conference-app/node_modules/ionic-gulp-browserify-es2015/node_modules/browserify/node_modules/resolve/lib/async.js:22:47
at FSReqWrap.oncomplete (fs.js:82:15)
Mind letting us know? https://github.com/driftyco/ionic-cli/issues
$ionic info
Your system information:
Cordova CLI: 6.1.1
Ionic Version: 2.0.0-beta.3
Ionic CLI Version: 2.0.0-beta.22
Ionic App Lib Version: 2.0.0-beta.12
OS:
Node Version: v4.4.2
Can anyone help me?
More than likely, you need to update NPM which will include the babelify dependencies. Check your version of NPM by running npm -v , it should be v3.x. Run sudo npm install -g npm to update npm. and you should be good to go.
Just npm install in project root worked for me.
Getting started with cloning a new Appcelerator project. I keep receiving this error. Many Appcelerator Google results are now archived and have not been able to access those Q/A.
I run the project via a Makefile that has:
all:
#${MAKE} clean
#${MAKE} compile
#${MAKE} run-sim
init:
...
#gittio install ti.airprint
#gittio install bencoding.blur
#gittio install de.marcelpociot.circularprogress
#${MAKE} all
After running make init. A long compilation process happens followed by the following
/Users/username/.nvm/versions/node/v0.12.7/bin/node /Users/username/.appcelerator/install/5.1.0/package/node_modules/appc-cli-titanium/node_modules/titanium/bin/titanium build --platform ios --plugin-paths /Users/username/.appcelerator/install/5.1.0/package/node_modules --config-file /var/folders/lj/c7hfzz254cd3lt2nxscv_wgw0000gn/T/build-1453310098056.json --log-level info --no-banner
[INFO] Found Titanium module id=bencoding.blur version=0.37 platform=iphone deploy-type=development path=/Users/username/Jester/cruisers-dealers/modules/iphone/bencoding.blur/0.37
[INFO] Found Titanium module id=de.marcelpociot.circularprogress version=1.1 platform=iphone deploy-type=development path=/Users/username/Jester/cruisers-dealers/modules/iphone/de.marcelpociot.circularprogress/1.1
[INFO] Found Titanium module id=ti.worker version=1.1.0 platform=iphone deploy-type=development path=/Users/username/Jester/cruisers-dealers/modules/iphone/ti.worker/1.1.0
[WARN] Could not find a valid Titanium module id=ti.airprint version=1.3.4 platform=iphone deploy-type=development
[INFO] Found Titanium module id=ti.cloud version=3.2.9 platform=commonjs deploy-type=development path=/Users/username/Library/Application Support/Titanium/modules/commonjs/ti.cloud/3.2.9
[ERROR] Could not find all required Titanium Modules:
[ERROR] id: ti.airprint version: 1.3.4 platform: iphone deploy-type: development
2016-01-20T17:15:02.058Z | ERROR | ti run exited with error code 1
make[2]: *** [run-sim] Error 1
make[1]: *** [all] Error 2
make: *** [init] Error 2
Update:
<modules>
<module platform="iphone" version="0.37">bencoding.blur</module>
<module platform="iphone" version="1.1">de.marcelpociot.circularprogress</module>
<module version="1.1.0" platform="iphone">ti.worker</module>
<module version="1.3.4" platform="iphone">ti.airprint</module>
<module platform="commonjs">ti.cloud</module>
</modules>
Update 2: After changing version on tiapp.xml to match that of the directory.
[Error: Module version mismatch. Expected 14, got 46.]
[ERROR] socket hang up
2016-01-20T18:16:24.368Z | ERROR | ti run exited with error code 100
make[2]: *** [run-sim] Error 1
make[1]: *** [all] Error 2
make: *** [init] Error 2
Changing the version number in tiapp.xml
<module version="1.3.4" platform="iphone">ti.airprint</module>
to match the projectname/modules/iphone/ti.airprint/1.4.3 did it for me. So this
<module version="1.3.4" platform="iphone">ti.airprint</module>
did it. I received other errors after doing this, but that is beyond this question.
You wrote 1.3.4 instead of 1.4.3, which is the correct version number.
1.3.4 is not existing in the releases: https://github.com/appcelerator-modules/ti.airprint/releases
The last error you see ([Error: Module version mismatch. Expected 14, got 46.]) happens when you've changed your NodeJS version. An Node (NPM) Module that uses native extensions will need to be rebuild if the NodeJS version has a different API then the previous. If you use ti then re-install that via NPM. If you use appc then do appc install 5.1.0 --force.
Appcelerator is working on detecting this and rebuilding for you.
I had compiled the module with a newer SDK than the one I was using in the project where I imported it. Appcelerator Studio pointed that out.