missing documentation for Angular 17's standalone mode

[rwaskiewicz]

In Angular v17, the Angular CLI generates applications in with components that use standalone mode by default. As a result, app.module.ts is not generated when a new application is generated.

The Stencil documentation, as written today, assumes the existence of said module in "Creating a Consumer Angular App":

From your Angular workspace (/packages/angular-workspace), run the following command to generate an Angular application:

npx -p @angular/cli ng generate app my-app

We then ask folks to modify the module in the subsequent section, "Consuming the Angular Wrapper Components":

If you distributed your components through a primary NgModule, you can simply import that module into an implementation to use your components.

// app.module.ts

import { ComponentLibraryModule } from 'component-library';

@NgModule({
imports: [ComponentLibraryModule],
})
export class AppModule {}

Moving forward, we should handle both pre and post-Angular 17. A few things we _could_ do:
- Inform folks of using `--standalone=false` when spinning up a component 
- Update the documentation to consume the libraries differently

[rwaskiewicz]

Closing. Fixed by #1284

If anyone should have questions surrounding the documentation, please feel free to open a new issue