Download Node V14.15.0
Kahlil Algya
I have a small pickle with how to setup my Babylon.js server side setup using NullEngine and TypeScript. I have a skeleton of a client side of the game done and I would like to share as much code as possible running the game server side. Trying to build kind of authoritative game server here
Basically I have a Game class, in Game.ts. It sets up all the game stuff, such picking if we should use regular engine or the null engine. So the first line in this Game.ts file is this:
import Engine, NullEngine from '@babylonjs/core'
After compiling this using tsc and trying to run with node server.js (or, just using ts-node), I get this error:
export * from "./abstractScene";
^^^^^^
SyntaxError: Unexpected token 'export'
As the title states, I'm currently running into issues when I try to start a local development server in the now-cli. There are two parts to this. After I successfully create a project, I run npm install to install my dependencies. During this time I get the following error:
gyp ERR! configure error
gyp ERR! stack Error: Command failed: /usr/bin/python3 -c import sys; print "%s.%s.%s" % sys.version_info[:3];
gyp ERR! stack File "", line 1
gyp ERR! stack import sys; print "%s.%s.%s" % sys.version_info[:3];
gyp ERR! stack ^
gyp ERR! stack SyntaxError: invalid syntax
gyp ERR! stack
gyp ERR! stack at ChildProcess.exithandler (child_process.js:308:12)
gyp ERR! stack at ChildProcess.emit (events.js:315:20)
gyp ERR! stack at maybeClose (internal/child_process.js:1048:16)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
gyp ERR! System Linux 5.8.18-200.fc32.x86_64
gyp ERR! command "/home/tdc/.nvm/versions/node/v14.15.0/bin/node" "/home/tdc/helloworld/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /home/tdc/helloworld/node_modules/node-sass
gyp ERR! node -v v14.15.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
Build failed with error code: 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.3 (node_modules/sane/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsev...@1.2.13: wanted "os":"darwin","arch":"any" (current: "os":"linux","arch":"x64")
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsev...@2.1.2 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsev...@2.1.3: wanted "os":"darwin","arch":"any" (current: "os":"linux","arch":"x64")
npm WARN @webpack-blocks/ba...@2.1.0 requires a peer of @babel/core@^7.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN babel-...@8.2.1 requires a peer of @babel/core@^7.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN sass-...@8.0.2 requires a peer of webpack@^4.36.0 ^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN enzyme-adap...@1.1.0 requires a peer of react-dom@^16.0.0-0 but none is installed. You must install peer dependencies yourself.
npm WARN react-tes...@16.14.0 requires a peer of react@^16.14.0 but none is installed. You must install peer dependencies yourself.
npm WARN karma-...@3.0.5 requires a peer of webpack@^2.0.0 ^3.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN @webpack-blocks/dev-s...@1.0.0 requires a peer of webpack@2.x 3.x but none is installed. You must install peer dependencies yourself.
npm WARN webpack-d...@2.11.5 requires a peer of webpack@^2.2.0 ^3.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN @webpack-blocks/web...@1.0.0 requires a peer of webpack@2.x 3.x but none is installed. You must install peer dependencies yourself.
npm WARN webpack-dev...@1.12.2 requires a peer of webpack@^1.0.0 ^2.0.0 ^3.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN extract-text-...@3.0.2 requires a peer of webpack@^3.1.0 but none is installed. You must install peer dependencies yourself.
npm WARN postcss-modules...@1.3.0 requires a peer of postcss@^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN acor...@5.3.1 requires a peer of acorn@^6.0.0 ^7.0.0 ^8.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN @tdc/hello...@0.0.1 No repository field.
npm WARN @tdc/hello...@0.0.1 No license field.
My first attempt was updating over the top of my existing node.js installation. I then tried uninstalling node.js installation (Windows Add/Remove Programs) and reinstalled. I ended up with the same error with npm.
This time around I could see the node.js installation was able to install an updated version of npm as well where it failed to upgrade an older npm if that folder already existed in my roaming profile.
Note the topics here are answered by the community or by the jsreport developers in their free time. ' + 'If you like a professional support or want to get a quick response you should purchase one of our support products. ' + 'The price is very reasonable and you can also help with further jsreport development this way. ' + 'You can choose from support products here. ' + 'With the support plan, you get access to the dedicated support portal and reach the jsreport core developers.
i see, using toLocaleString relies on the icu information of the node.js version, in normal case using nodejs 14.15.0 is enough because it comes with the full icu information so all locales should work ok here. i did a simple test and this works ok with 14.15.0
this is probably the problem for your case, you have nodejs 14.15 installed however if you use the docker container then you end up using the nodejs version which is specified in the Docker build, which in the case of the jsreport 2.8.0 is nodejs 12, which does not come with the full icu needed to support all locales.
I browsed the forum for similar issues. Running npm cache verify and sudo npm cache verify did not resolve the issue. I am not knowledgeable with node so apologies if there is something simple here, and appreciate all the help.
Thank you for the quick response. After tinkering around and reading through this and this, I decided to use nvm to install node and npm instead of using the debian unstable package. The other option was to fix the permissions for /usr/lib/nodejs after installing the package, which I did not prefer.
I am new in the SPFx development, I have installed the Node.js 16.14.0 and I have run the commands as per the -us/sharepoint/dev/spfx/set-up-your-development-environment#install-nodejs. But, when I have run the following command it stuck.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
SharePoint Framework v1.14 is not compatible with Node.js v14.0.0. As mentioned in my original answer, you need Node.js v14.15.0 or later. To get a compatible version of Node.js, please follow these steps.
I have installed node.js v14.19.0 and then I have created the new test project its working. But, when I am open the existing project and run the gulp serve command its give me following error. Kindly help me to solve this production error.
I'm setting up Cloud Elastic APM with a node/express/postgres server. The web requests are coming in as expected, however, only the postgresql START and COMMIT commands from the transactions are being shown but not the queries themselves.
When I set the logs to "trace", I can see the query is being intercepted from pg (see below), but for some reason it's not logged. The only difference between the queries that are logged (START/COMMIT) and the ones that are not, is that the ones logged have IDs and the main query does not. However, I'm not sure if that's important. I also notice that it says "no active transaction found - cannot build new span".
I have enabled the pg_stat_statements extension in postgres as recommended in this post. However, I'm not sure that would do anything since it appears that the APM module intercepts queries directly from pg.
As a point of reference, do you need to add the sonar.nodejs.executable in to the Additional Settings of the Prepare the SonarQube analysis Build Step. Or can you add it Globally into the SonarQube Instance in the sonar.properties file?
Hi Nagla_aly
I am also having same issue where Javascript and css files are not getting scanned.
I have gone through the mavan command execution errors and seen that node js installed path not available.
If you local machine have latest version of Node JS installed and set environment path variables then you no need to mention in sonar.properties file, Sonar cube will take automatically from environment path variables like below.
I posted my issue before, but there were no responses. I am tryining to install adapt authoring on my Ubunutu server 20.04.01 LTE. All Prerequisites are installed. Node is on the current LTS version v14.15.0.
We need to configure the tool before install.
Tip: just press ENTER to accept the default value in brackets.
? Server port 5000
? Server name localhost
? Data directory path data
? Git repository URL to be used for the authoring tool source code _authoring.git
? Git repository URL to be used for the framework source code _framework.git
? Specific git revision to be used for the framework. Accepts any valid revision type (e.g. branch/tag/commit) tags/v5.7.1
? Master database name adapt-tenant-master
? Will you be using a full database connection URI? (all connection options in the URI) No
? Database host localhost
? Database server port 27017
? Database server user (only specify if using database authentication)
? Database server password (only specify if using database authentication)
? Database server authentication database (only specify if using database authentication)
? Will you be using an SMTP server? (used for sending emails) No
Now we need to configure the master tenant.
Tip: just press ENTER to accept the default value in brackets.