2,063When running 'Yarn Start' in Visual Studio Code I get some errors that I don't understand. It only happens on 9.36. When switching to 9.35 it don't fail:
Here are the error :
Starting type checking service...
Using 1 worker with 4096MB memory limit
No type errors found
Version: typescript 3.9.10, eslint 7.32.0
Time: 6457ms
Starting type checking service...
Webpack: Starting ...
√ Compile modules
√ Build modules
√ Optimize modules
√ Emit files
Webpack: Finished after 40.569 seconds.
No type errors found
Version: typescript 3.9.10, eslint 7.32.0
Time: 5989ms
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
ApplicationInsights:An invalid instrumentation key was provided. There may be resulting telemetry loss [ ' ' ]
partner server only actions registration file not found. Error: Cannot find module 'lib/server-only-actions-registration'
at webpackMissingModule (C:\repos\Msdyn365.Commerce.Online\build\webpack:\node_modules\@msdyn365-commerce\bootloader\entry\bootstrap.js?d994:82:55)
at initServerOnlyActions (C:\repos\Msdyn365.Commerce.Online\build\webpack:\node_modules\@msdyn365-commerce\bootloader\entry\bootstrap.js?d994:82:55)
at Module../node_modules/@msdyn365-commerce/bootloader/entry/bootstrap.js (C:\repos\Msdyn365.Commerce.Online\build\webpack:\node_modules\@msdyn365-commerce\bootloader\entry\bootstrap.js?d994:227:1)
at __webpack_require__ (C:\repos\Msdyn365.Commerce.Online\build\webpack:\webpack\bootstrap?7f80:754:1)
at require (C:\repos\Msdyn365.Commerce.Online\build\webpack:\webpack\bootstrap?7f80:59:1)
at Object../node_modules/@msdyn365-commerce/bootloader/entry/index.js (C:\repos\Msdyn365.Commerce.Online\build\webpack:\node_modules\@msdyn365-commerce\bootloader\entry\index.js?c631:23:5)
at __webpack_require__ (C:\repos\Msdyn365.Commerce.Online\build\webpack:\webpack\bootstrap?7f80:754:1)
at fn (C:\repos\Msdyn365.Commerce.Online\build\webpack:\webpack\bootstrap?7f80:59:1)
at Object.0 (C:\repos\Msdyn365.Commerce.Online\build\server.js:563525:18)
at __webpack_require__ (C:\repos\Msdyn365.Commerce.Online\build\webpack:\webpack\bootstrap?7f80:754:1) {
code: 'MODULE_NOT_FOUND'
}
partner server only actions local registration file not found. Error: Cannot find module 'lib/server-only-actions-registration.local'
at webpackMissingModule (C:\repos\Msdyn365.Commerce.Online\build\webpack:\node_modules\@msdyn365-commerce\bootloader\entry\bootstrap.js?d994:97:62)
at initServerOnlyActions (C:\repos\Msdyn365.Commerce.Online\build\webpack:\node_modules\@msdyn365-commerce\bootloader\entry\bootstrap.js?d994:97:62)
at Module../node_modules/@msdyn365-commerce/bootloader/entry/bootstrap.js (C:\repos\Msdyn365.Commerce.Online\build\webpack:\node_modules\@msdyn365-commerce\bootloader\entry\bootstrap.js?d994:227:1)
at __webpack_require__ (C:\repos\Msdyn365.Commerce.Online\build\webpack:\webpack\bootstrap?7f80:754:1)
at require (C:\repos\Msdyn365.Commerce.Online\build\webpack:\webpack\bootstrap?7f80:59:1)
at Object../node_modules/@msdyn365-commerce/bootloader/entry/index.js (C:\repos\Msdyn365.Commerce.Online\build\webpack:\node_modules\@msdyn365-commerce\bootloader\entry\index.js?c631:23:5)
at __webpack_require__ (C:\repos\Msdyn365.Commerce.Online\build\webpack:\webpack\bootstrap?7f80:754:1)
at fn (C:\repos\Msdyn365.Commerce.Online\build\webpack:\webpack\bootstrap?7f80:59:1)
at Object.0 (C:\repos\Msdyn365.Commerce.Online\build\server.js:563525:18)
at __webpack_require__ (C:\repos\Msdyn365.Commerce.Online\build\webpack:\webpack\bootstrap?7f80:754:1) {
code: 'MODULE_NOT_FOUND'
}
Mobx observer: You are using 'observer' on React.PureComponent. These two achieve two opposite goals and should not be used together
Mobx observer: You are using 'observer' on React.PureComponent. These two achieve two opposite goals and should not be used together
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Mobx observer: You are using 'observer' on React.PureComponent. These two achieve two opposite goals and should not be used together
Mobx observer: You are using 'observer' on React.PureComponent. These two achieve two opposite goals and should not be used together
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Mobx observer: You are using 'observer' on React.PureComponent. These two achieve two opposite goals and should not be used together
Mobx observer: You are using 'observer' on React.PureComponent. These two achieve two opposite goals and should not be used together
Mobx observer: You are using 'observer' on React.PureComponent. These two achieve two opposite goals and should not be used together
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
<--- Last few GCs --->
[2776:000002A5230AE810] 100100 ms: Mark-sweep 2037.2 (2061.9) -> 2033.1 (2052.6) MB, 231.2 / 0.2 ms (+ 598.5 ms in 122 steps since start of marking, biggest step 11.2 ms, walltime since start of marking 889 ms) (average mu = 0.138, current mu = 0.093)
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Mobx observer: You are using 'observer' on React.PureComponent. These two achieve two opposite goals and should not be used together
Mobx observer: You are using 'observer' on React.PureComponent. These two achieve two opposite goals and should not be used together
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Mobx observer: You are using 'observer' on React.PureComponent. These two achieve two opposite goals and should not be used together
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Mobx observer: You are using 'observer' on React.PureComponent. These two achieve two opposite goals and should not be used together
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Mobx observer: You are using 'observer' on React.PureComponent. These two achieve two opposite goals and should not be used together
Mobx observer: You are using 'observer' on React.PureComponent. These two achieve two opposite goals and should not be used together
Mobx observer: You are using 'observer' on React.PureComponent. These two achieve two opposite goals and should not be used together
Mobx observer: You are using 'observer' on React.PureComponent. These two achieve two opposite goals and should not be used together
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Mobx observer: You are using 'observer' on React.PureComponent. These two achieve two opposite goals and should not be used together
Mobx observer: You are using 'observer' on React.PureComponent. These two achieve two opposite goals and should not be used together
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Mobx observer: You are using 'observer' on React.PureComponent. These two achieve two opposite goals and should not be used together
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
1: 00007FF7401E3B5F napi_wrap+119263
2: 00007FF74018A4A6 v8::internal::OrderedHashTable<v8::internal::OrderedHashSeMobx observer: You are using 'observer' on React.PureComponent. These two achieve two opposite goalded when using mobx-react.
14: 00007FF7400AB4A1 node::SetTracingController+40753
15: 00007FF7400AB291 node::SetTracingController+40225
16: 00007FF74017571D v8::internal::OrderedHashTable<v8::internal::OrderedHashSet,1>::NumberOfBucketsOffset+223741
17: 00007FF7402396B7 uv_timer_stop+775
Mobx observer: You are using 'observer' on React.PureComponent. These two achieve two opposite goals and should not be used together
18: 00007FF740235EFB uv_async_send+33119: 00007FF74023567C uv_loop_init+1276
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
20: 00007FF74023582C uv_run+220
21: 00007FF740140C81 v8::internal::OrderedHashTable<v8::internal::OrderedHashSet,1>::NumMobx observer: You are using 'observer' on React.PureComponent. These two achieve two opposite goals and should not be used together
berOfBucketsOffset+8033Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
22: 00007FF7401B4F45 node::Start+293
23: 00007FF740016B5C RC4_options+34057224: 00007FF740ED75A8 v8::internal::SetupIsolateDelegate::SetupHeap+1300824
Use `shouldComponentUpdate` in an `observer` based component breaks the behavior of `observer` and might lead to unexpected results. Manually implementing `sCU` should not be needed when using mobx-react.
25: 00007FF80FBC244D BaseThreadInitThunk+2926: 00007FF811DEDF88 RtlUserThreadStart+40
error Command failed with exit code 134.
info Visit yarnpkg.com/.../run for documentation about this command.
error Command failed with exit code 134.
info Visit yarnpkg.com/.../run for documentation about this command.
PS C:\repos\Msdyn365.Commerce.Online>
