[INFO REQ] Running the aspnet demo

[ynoth]

I have just downloaded the trail version and I’m having an issue with the aspnet demo when building the javascript application (npm install && npm run build) – this is the error log. Do you have any ideas?

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 'run',
1 verbose cli 'build'
1 verbose cli ]
2 info using npm@6.14.6
3 info using node@v12.18.3
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle bryntum-schedulerpro-net-demo@1.0.0_prebuild: bryntum-schedulerpro-net-demo@1.0.0
6 info lifecycle bryntum-schedulerpro-net-demo@1.0.0_build: bryntum-schedulerpro-net-demo@1.0.0
7 verbose lifecycle bryntum-schedulerpro-net-demo@1.0.0_build: unsafe-perm in lifecycle true
8 verbose lifecycle bryntum-schedulerpro-net-demo@1.0.0_build: PATH:……
9 verbose lifecycle bryntum-schedulerpro-net-demo@1.0.0_build: CWD: C:\clients\Bryntum Scheduler\schedulerpro-1.0.2-trial\examples-scheduler\aspnet\BryntumSchedulerCrudDemo\app
10 silly lifecycle bryntum-schedulerpro-net-demo@1.0.0_build: Args: [ '/d /s /c', 'webpack --config webpack.config.js --progress' ]
11 silly lifecycle bryntum-schedulerpro-net-demo@1.0.0_build: Returned: code: 2 signal: null
12 info lifecycle bryntum-schedulerpro-net-demo@1.0.0_build: Failed to exec build script
13 verbose stack Error: bryntum-schedulerpro-net-demo@1.0.0 build: webpack --config webpack.config.js --progress
13 verbose stack Exit status 2
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:315:20)
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:315:20)
13 verbose stack at maybeClose (internal/child_process.js16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid bryntum-schedulerpro-net-demo@1.0.0
15 verbose cwd C:\clients\Bryntum Scheduler\schedulerpro-1.0.2-trial\examples-scheduler\aspnet\BryntumSchedulerCrudDemo\app
16 verbose Windows_NT 10.0.17763
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "build"
18 verbose node v12.18.3
19 verbose npm v6.14.6
20 error code ELIFECYCLE
21 error errno 2
22 error bryntum-schedulerpro-net-demo@1.0.0 build: webpack --config webpack.config.js --progress
22 error Exit status 2
23 error Failed at the bryntum-schedulerpro-net-demo@1.0.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 2, true ]

[Maxim Gorkovsky]

Hello.
I can see the problem in the distribution. I opened a ticket to investigate this issue: https://github.com/bryntum/support/issues/1314
As a workaround I can recommend to go to node_modules and replace bryntum-schedulerpro symlink with an actual copy of the folder. Apparently bundle is trying to resolve packages relative to its absolute path, which is outside of the example.

[ynoth]

Thanks, that appears to work as a workaround for now

[sergey.maltsev]

Hi, ynoth!

You could try this workaround also.

Add symlinks resolve rule to false in webpack.config like this

module.exports = [
    {
        entry : {
            cruddemo : path.join(__dirname, 'app.js')
        },
        resolve: {
            symlinks: false
        },
     ...

Do this for all demos.

[ynoth]

Thanks will do that