Thank you very much!
Yes, I have updated Angular recently. And yes the initial/standard pages are all working.
I will send through the specific feature branch I have been playing around with to the email address below. Do you want all of it?
Thank you for getting back to me. As always, I am very grateful for the help you all provide and I think you are doing a great job with the platform.
I forgot to run yarn after I had added the reference into package.json. Once this was done the problem went away!
Hi,
Thank you for sharing. I am trying to do a similar thing. However, I am facing a few problems. When you were implementing this, did you encounter the following problem with the draggable.js script in ngAfterViewInit (and if so, did you find a solution):
ERROR in src/app/main/demographics/patient-details/patient-details.component.ts(95,25): error TS2345: Argument of type '{ connectWith: string; items: string; opacity: number; handle: string; coneHelperSize: boolean; p...' is not assignable to parameter of type 'SortableOptions'. Object literal may only specify known properties, but 'coneHelperSize' does not exist in type 'SortableOptions'. Did you mean to write 'forceHelperSize'? src/app/main/demographics/patient-details/patient-details.component.ts(100,25): error TS1117: An object literal cannot have multiple properties with the same name in strict mode. src/app/main/demographics/patient-details/patient-details.component.ts(100,25): error TS2300: Duplicate identifier 'tolerance'. src/app/main/demographics/patient-details/patient-details.component.ts(101,25): error TS1117: An object literal cannot have multiple properties with the same name in strict mode. src/app/main/demographics/patient-details/patient-details.component.ts(101,25): error TS2300: Duplicate identifier 'forcePlaceholderSize'. src/app/main/demographics/patient-details/patient-details.component.ts(102,25): error TS1117: An object literal cannot have multiple properties with the same name in strict mode. src/app/main/demographics/patient-details/patient-details.component.ts(102,25): error TS2300: Duplicate identifier 'helper'.
C:\Repos\Danely\angular>ng -v
_ _ ____ _ ___
/ \ _ __ __ _ _ _| | __ _ _ __ / ___| | |_ _|
/ △ \ | '_ \ / _` | | | | |/ _` | '__| | | | | | |
/ ___ \| | | | (_| | |_| | | (_| | | | |___| |___ | |
/_/ \_\_| |_|\__, |\__,_|_|\__,_|_| \____|_____|___|
|___/
Angular CLI: 6.0.0
Node: 8.9.3
OS: win32 x64
Angular: 6.0.0
... animations, cli, common, compiler, compiler-cli, core, forms
... http, platform-browser, platform-browser-dynamic
... platform-server, router
Package Version
-----------------------------------------------------------
@angular-devkit/architect 0.6.0
@angular-devkit/build-angular 0.6.1
@angular-devkit/build-optimizer 0.6.1
@angular-devkit/core 0.6.0
@angular-devkit/schematics 0.6.0
@ngtools/webpack 6.0.1
@schematics/angular 0.6.0
@schematics/update 0.6.0
rxjs 6.1.0
typescript 2.7.2
webpack 4.6.0
Thank you for getting back. I looked at that as well. Below is the full tsconfig.json file
{ "compilerOptions": { "declaration": false, "emitDecoratorMetadata": true, "experimentalDecorators": true, "lib": [ "es6", "dom" ], "mapRoot": "./", "module": "es6", "skipLibCheck": true, "moduleResolution": "node", "outDir": "../dist/out-tsc", "sourceMap": true, "target": "es5", "typeRoots": [ "../node_modules/@types" ], "baseUrl": ".", "paths": { "@abp/": [ "../node_modules/abp-ng2-module/dist/src/" ], "@app/": [ "./app/" ], "@shared/": [ "./shared/" ], "@node_modules/": [ "../node_modules/" ], "@angular/": [ "../node_modules/@angular/" ] } }, "exclude": [ "node_modules" ] }
I can now compile and run the application. The only "problem" is that it takes a loooong time to complete the sourcemap process. There is a lot of people talking about getting stuck on 92% when reading various forums (see for instance <a class="postlink" href="https://stackoverflow.com/questions/49184787/92-chunk-asset-optimization-webpack">https://stackoverflow.com/questions/491 ... on-webpack</a> ) . Before upgrading to 5.4.1 I don't recall this taking minutes, but it is now. If I am the only one with this problem then it could be a merge problem or something else I have done...
That was the first I tried (After deleting yarn.lock and running yarn again). I then tried lots of different things but I think it was running ng build that finally fixed it. Still hangs on 92% when running npm start...
OK, thank you for the help!
I tried to create a Folder under wwwroot already. That didn't work (it stopped complaining about the folder not existing, but still got the 500 error - but I couldn't find anything in the logs to say why).
Had same problem.
Merged version 5.3 into my project. Worked fine locally, but 5.3 failed with strange error code 500 when running in Azure. (Took a while to find the problem because very little useful logging were provided). I am not using Plugins (yet) so not an issue to comment out this line...