V10 , script for dynamic builds

Even with 9.0 I ended up writing my own PowerShell script that does all the leg work, and prompts for loading of individual components (after qer/qbm), also opens in tabs rather than windows like VST... VST was just too annoying with the way it did it.

Hello Ben 
would you maybe share this script?

I've no issues with these versions. Just to be sure you already did:
npm cache clean --force
rm -rf node_modules/
npm install

Everything I read is that npm fixed their cache handling quite some time back and they all say a "cache clean" does nothing now (my script above, when run, will do some cleaning as well before trying to run/start).

Also, as it was directly from a downloaded from repo (as zip) and extracted, there is no node_modules, so my install above was what populated it (i.e. all fresh downloads). I've even done a full nvm removal of nodejs and deleted the entire repo, then started again with same results.

We do use ZScalar on our work machines, so who knows if that has stuffed something in transit...

I know a colleague managed to get the builds running on the client before Christmas (just testing to identify any base issues prior to their upgrade in the next month or so)...problem I have, is that NodeJS/npm is so damn annoying to debug ("UNKNOWN" error is not really helpful). I'll try diagnosing node_modules\chokidar\handler.js on Tuesday to see if it can assist with identifying issue.

Big fat swears.... Path depth/location....

Although now, I see that components won't compile with dynamic.... (qbm and qer were fine with "npm run build:watch ") - I'm guessing dynamic really is dead?

npm run build:watch:dynamic tsb => "Error: Missing script: "build:watch:dynamic""

ng build --watch --configuration dynamic tsb => "[error] Error: Configuration 'dynamic' for target 'build' in project 'tsb' is not set in the workspace."

And the big wheel has completed a turn and we're back where we started. Ben  

This is why I created this thread. So far we're debugging tsb with npm run build:watch tsb , and that seems to work.

Maybe tsb is not a plugin anymore xD The documentation has not been fixed, nor anyone involved said otherwise, yet.

juancarlos camargo It's so funny whenever things come full circle ;-)
Did you see this one: github.com/.../334

I was reading that there is now a different method for "dynamic" equivalence, the Issue Niels de Groot linked below appears to say that "dynamic" was actually removed.

A Google search for "ng add dynamic configuration to angular" gives back some Gemini info (probably rubbish, but will run with it) that suggests a new set of functions do the equivalent within the component, rather than the old "dynamic script" - seems to get it from this Stack Overflow post.

I've also updated the script above -  RE: V10 , script for dynamic builds 

Thanks Niels de Groot !

I had not, but anyway., I had all my code migrated to 9.3.1 when v10 came up, so I restarted over . In v9.3.1 there was still support for dynamic building, which has been corrected or modified or omitted in v10. But your link provided all the necessary info, so my s

Interestingly, I just had a converstation with a colleague who has been trying nx instead of npm and says that its much better as, its a single command that automatically build dependencies, and it appears to be better performing. However, watch scripts are missing, never mind dynamic 

Caches are giving me more than a headache 

I'm running my custom component with dynamic and everytime I save it I need to check carefully if the compiler is taking this or what cache version. 

Source:
Line 27: <ng-container [matColumnDef]="entitySchemaPersonReports?.Columns?.CCC_DepartmentFullPath?.ColumnName">
            
Compiler says:
ERROR: projects/cvu/src/lib/identidades/identities.component.html:27:43 - error TS2339: Property 'CCC_DepartmentFullPath' does not exist on type 'CvuIdentitiesComponent'.      

27             <ng-container [matColumnDef]="CCC_DepartmentFullPath">
                                             ~~~~~~~~~~~~~~~~~~~~~~

and no matter how I modify the line, it keeps saying the same. I need to stop the npm run buid:watch and rerun it, and then restart serving the app, so debugging it's taking ages.

Well, that just proves they haven't put in the alternate code that is supposed to work without dynamic.... this all sounds like a complete pain in the posterior

Well, that just proves they haven't put in the alternate code that is supposed to work without dynamic.... this all sounds like a complete pain in the posterior