npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@evolv/angular-execution-plan

v0.0.3

Published

Angular can introduce extra timing concerns to updating the page in an Evolv project. It is not uncommon that Evolv can render the project changes, then have Angular update the DOM over the top.

Downloads

8

Readme

Evolv Execution-Plan Angular Integration

Angular can introduce extra timing concerns to updating the page in an Evolv project. It is not uncommon that Evolv can render the project changes, then have Angular update the DOM over the top.

This library gives extra control over Evolv's functionality on the page.

Importing the Library

Include in your project by running

npm install @evolv/angular-execution-plan

Directives

Evolv provides directives to automatically apply project changes based on Angular lifecycle hooks.

e.g. Include the AfterViewInitDirective and mark components with evolvAfterViewInit

<mat-horizontal-stepper>
  <mat-step evolvAfterViewInit>
    <ng-template matStepLabel>Payment</ng-template>
  </mat-step>
  <mat-step evolvAfterViewInit>
    <ng-template matStepLabel>Confirm</ng-template>
  </mat-step>
</mat-horizontal-stepper>

Direct Runtime Access

The ExecutionPlanService provides direct access to the Evolv execution plan and the runtime.

This allows you to directly reapply any changes

@Component({
  selector: 'example',
  templateUrl: './example.component.html',
  styleUrls: ['./example.component.scss']
})
export class ExampleComponent {
  private runtime: any;

  constructor(evolv: ExecutionPlanService) {
    this.runtime = evolv.getRuntime();
  }

  manualRun = async (event) => {
    (await this.runtime).rerun();
  }
}

To configure how long you are willing to wait for Evolv to be present on the page, provide a custom value for the timeout

@NgModule({
  declarations: [
    AppComponent, ...
  ],
  imports: [
    ExecutionPlanModule, ...
  ],
  providers: [
    {provide: EXECUTION_PLAN_MAX_WAIT, useValue: 200 }
  ],
  ...
})

You can also directly access the Evolv instance and call any of the native functionality

@Component({
  selector: 'example',
  templateUrl: './example.component.html',
  styleUrls: ['./example.component.scss']
})
export class ExampleComponent {
  private evolv: any;

  constructor(evolv: ExecutionPlanService) {
    this.evolv = evolv.getEvolv();
    (await this.evolv).on()
  }

  manualRun = async (event) => {
    (await this.runtime).on('stagecompleted', () => console.log('stagecompleted'));
  }
}

You can find an example site implementing these features here

Development

Code scaffolding

Run ng generate component component-name --project execution-plan to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module --project execution-plan.

Note: Don't forget to add --project execution-plan or else it will be added to the default project in your angular.json file.

Build

Run ng build execution-plan to build the project. The build artifacts will be stored in the dist/ directory.

Publishing

After building your library with ng build execution-plan, go to the dist folder cd dist/execution-plan and run npm publish.

Running unit tests

Run ng test execution-plan to execute the unit tests via Karma.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI README.