Developer edition offline install

1590
9
04-16-2020 06:18 PM
LeonAus
New Contributor III

I'm getting an error when trying to start the developer edition after following Jianxia Song's instructions of:

 

'The workaround we have is to get the modules from another place that has the internet installed, then copy the node module folder over to your environment without the internet. Keep in mind, the node version from both places should be the same. Otherwise, you may run into problems. Hope this helps.'

 

The node version is the same on the workstation where I downloaded the modules and where I am trying to run.

 

The error is:

D:\eGIS\Working\Leon\egis_dev\ExperienceBuilder_1.0\server>npm start

> exb-server@0.1.0 start D:\eGIS\Working\Leon\egis_dev\ExperienceBuilder_1.0\server
> cross-env NODE_ENV=production node src/server

internal/modules/cjs/loader.js:800
throw err;
^

Error: Cannot find module '../../global'
Require stack:
- D:\eGIS\Working\Leon\egis_dev\ExperienceBuilder_1.0\server\node_modules\exb-history-404\index.js
- D:\eGIS\Working\Leon\egis_dev\ExperienceBuilder_1.0\server\src\server.js
←[90m at Module._resolveFilename (internal/modules/cjs/loader.js:797:15)←[39m
at Function.Module._resolveFilename (D:\eGIS\Working\Leon\egis_dev\ExperienceBuilder_1.0\server\node_modules\←[4mexb-ssr←[24m\index.js:1:9904)
←[90m at Function.Module._load (internal/modules/cjs/loader.js:690:27)←[39m
←[90m at Module.require (internal/modules/cjs/loader.js:852:19)←[39m
←[90m at require (internal/modules/cjs/helpers.js:74:18)←[39m
at Object.<anonymous> (D:\eGIS\Working\Leon\egis_dev\ExperienceBuilder_1.0\server\node_modules\←[4mexb-history-404←[24m\index.js:1:2289)
←[90m at Module._compile (internal/modules/cjs/loader.js:959:30)←[39m
←[90m at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)←[39m
←[90m at Module.load (internal/modules/cjs/loader.js:815:32)←[39m
←[90m at Function.Module._load (internal/modules/cjs/loader.js:727:14)←[39m {
code: ←[32m'MODULE_NOT_FOUND'←[39m,
requireStack: [
←[32m'D:\\eGIS\\Working\\Leon\\egis_dev\\ExperienceBuilder_1.0\\server\\node_modules\\exb-history-404\\index.js'←[39m,
←[32m'D:\\eGIS\\Working\\Leon\\egis_dev\\ExperienceBuilder_1.0\\server\\src\\server.js'←[39m
]
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! exb-server@0.1.0 start: `cross-env NODE_ENV=production node src/server`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the exb-server@0.1.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\vyXXXX\AppData\Roaming\npm-cache\_logs\2020-04-17T01_05_37_572Z-debug.log

 

The debug log file reports:

 

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'start'
1 verbose cli ]
2 info using npm@6.12.1
3 info using node@v12.13.1
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle exb-server@0.1.0~prestart: exb-server@0.1.0
6 info lifecycle exb-server@0.1.0~start: exb-server@0.1.0
7 verbose lifecycle exb-server@0.1.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle exb-server@0.1.0~start: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;D:\eGIS\Working\Leon\egis_dev\ExperienceBuilder_1.0\server\node_modules\.bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\Git\cmd;E:\ArcGIS\Pro\bin\Python\envs\arcgispro-py3;C:\Program Files\nodejs\;C:\Users\vyXXXX\AppData\Roaming\npm
9 verbose lifecycle exb-server@0.1.0~start: CWD: D:\eGIS\Working\Leon\egis_dev\ExperienceBuilder_1.0\server
10 silly lifecycle exb-server@0.1.0~start: Args: [ '/d /s /c', 'cross-env NODE_ENV=production node src/server' ]
11 silly lifecycle exb-server@0.1.0~start: Returned: code: 1 signal: null
12 info lifecycle exb-server@0.1.0~start: Failed to exec start script
13 verbose stack Error: exb-server@0.1.0 start: `cross-env NODE_ENV=production node src/server`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:210:5)
13 verbose stack at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:210:5)
13 verbose stack at maybeClose (internal/child_process.js:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
14 verbose pkgid exb-server@0.1.0
15 verbose cwd D:\eGIS\Working\Leon\egis_dev\ExperienceBuilder_1.0\server
16 verbose Windows_NT 6.3.9600
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v12.13.1
19 verbose npm v6.12.1
20 error code ELIFECYCLE
21 error errno 1
22 error exb-server@0.1.0 start: `cross-env NODE_ENV=production node src/server`
22 error Exit status 1
23 error Failed at the exb-server@0.1.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

 

Any ideas what I'm doing wrong?

 

Thanks.

0 Kudos
9 Replies
Jianxia
Esri Regular Contributor

Junhan Liu‌ could you take a look?

0 Kudos
JunshanLiu
Occasional Contributor III

I tried some ways but don't find a way to install successfully.

I'll create an issue in our repo to try to figure out a way.

LeonAus
New Contributor III

Hi,

Is there a rough time frame for when this will be resolved? Is it being looked at now or has it been deferred?

Thanks,
Leon.

0 Kudos
Jianxia
Esri Regular Contributor

Leon,

We plan to fix it in the upcoming release in July. Thanks for being patient with us. 

0 Kudos
JoeHershman
MVP Regular Contributor

I found that running:

npm set strict-ssl false

Resolved the issue

0 Kudos
Jianxia
Esri Regular Contributor

Wow, that's awesome. Thanks for sharing.

0 Kudos
JoeHershman
MVP Regular Contributor

Is there a solution to this?  I have run as admin which does not make any difference.  Run from node.js prompt and standard command prompt.

Tried this: node.js - Laravel 5.4 ‘cross-env’ Is Not Recognized as an Internal or External Command - Stack Overf... 

still no luck.  Why cannot I not run?

Thanks

-Joe

0 Kudos
Jianxia
Esri Regular Contributor

Joe,

We are looking into the solution.

0 Kudos
JunshanLiu
Occasional Contributor III

@Leon Woodhouse Can you try this way?

1. Pack npm cache. On a computer with internet connection:
1.1 Clean cache, run: npm cache clean -f
1.2 Install modules. In <install folder>/server and  <install folder>/client directory, run: npm ci
1.3 Find the cache directory location, run: npm config get cache
1.4 Pack npm-cache directory(zip it)


2. Use the packed cache. On the offline computer:
2.1 Find the cache directory location, run: npm config get cache
2.2 Replace the npm-cache with packed npm-cache in step 1.
2.3 In <install folder>/server and  <install folder>/client directory, run : npm install --offline

0 Kudos