LogoLogo
HomeDiscourseBlogDiscord
  • Introduction
  • Introduction
    • Quick start
    • Aurelia for new developers
    • Hello world
      • Creating your first app
      • Your first component - part 1: the view model
      • Your first component - part 2: the view
      • Running our app
      • Next steps
  • Templates
    • Template Syntax
      • Attribute binding
      • Event binding
      • Text interpolation
      • Template promises
      • Template references
      • Template variables
      • Globals
    • Custom attributes
    • Value converters (pipes)
    • Binding behaviors
    • Form Inputs
    • CSS classes and styling
    • Conditional Rendering
    • List Rendering
    • Lambda Expressions
    • Local templates (inline templates)
    • SVG
  • Components
    • Component basics
    • Component lifecycles
    • Bindable properties
    • Styling components
    • Slotted content
    • Scope and context
    • CustomElement API
    • Template compilation
      • processContent
      • Extending templating syntax
      • Modifying template parsing with AttributePattern
      • Extending binding language
      • Using the template compiler
      • Attribute mapping
  • Getting to know Aurelia
    • Routing
      • @aurelia/router
        • Getting Started
        • Creating Routes
        • Routing Lifecycle
        • Viewports
        • Navigating
        • Route hooks
        • Router animation
        • Route Events
        • Router Tutorial
        • Router Recipes
      • @aurelia/router-lite
        • Getting started
        • Router configuration
        • Configuring routes
        • Viewports
        • Navigating
        • Lifecycle hooks
        • Router hooks
        • Router events
        • Navigation model
        • Transition plan
    • App configuration and startup
    • Enhance
    • Template controllers
    • Understanding synchronous binding
    • Dynamic composition
    • Portalling elements
    • Observation
      • Observing property changes with @observable
      • Effect observation
      • HTML observation
      • Using observerLocator
    • Watching data
    • Dependency injection (DI)
    • App Tasks
    • Task Queue
    • Event Aggregator
  • Developer Guides
    • Animation
    • Testing
      • Overview
      • Testing attributes
      • Testing components
      • Testing value converters
      • Working with the fluent API
      • Stubs, mocks & spies
    • Logging
    • Building plugins
    • Web Components
    • UI virtualization
    • Errors
      • 0001 to 0023
      • 0088 to 0723
      • 0901 to 0908
    • Bundlers
    • Recipes
      • Apollo GraphQL integration
      • Auth0 integration
      • Containerizing Aurelia apps with Docker
      • Cordova/Phonegap integration
      • CSS-in-JS with Emotion
      • DOM style injection
      • Firebase integration
      • Markdown integration
      • Multi root
      • Progress Web Apps (PWA's)
      • Securing an app
      • SignalR integration
      • Strongly-typed templates
      • TailwindCSS integration
      • WebSockets Integration
      • Web Workers Integration
    • Playground
      • Binding & Templating
      • Custom Attributes
        • Binding to Element Size
      • Integration
        • Microsoft FAST
        • Ionic
    • Migrating to Aurelia 2
      • For plugin authors
      • Side-by-side comparison
    • Cheat Sheet
  • Aurelia Packages
    • Validation
      • Validation Tutorial
      • Plugin Configuration
      • Defining & Customizing Rules
      • Architecture
      • Tagging Rules
      • Model Based Validation
      • Validation Controller
      • Validate Binding Behavior
      • Displaying Errors
      • I18n Internationalization
      • Migration Guide & Breaking Changes
    • i18n Internationalization
    • Fetch Client
      • Overview
      • Setup and Configuration
      • Response types
      • Working with forms
      • Intercepting responses & requests
      • Advanced
    • Event Aggregator
    • State
    • Store
      • Configuration and Setup
      • Middleware
    • Dialog
  • Tutorials
    • Building a ChatGPT inspired app
    • Building a realtime cryptocurrency price tracker
    • Building a todo application
    • Building a weather application
    • Building a widget-based dashboard
    • React inside Aurelia
    • Svelte inside Aurelia
    • Synthetic view
    • Vue inside Aurelia
  • Community Contribution
    • Joining the community
    • Code of conduct
    • Contributor guide
    • Building and testing aurelia
    • Writing documentation
    • Translating documentation
Powered by GitBook
On this page
  • Setup
  • packages
  • packages-tooling

Was this helpful?

Export as PDF
  1. Community Contribution

Building and testing aurelia

Get setup to build and test the Aurelia 2 source!

PreviousContributor guideNextWriting documentation

Last updated 2 years ago

Was this helpful?

If you're looking to contribute directly to Aurelia or its test suite, you've come to the right place!

Here's what you'll learn...

  • Setting up your machine and cloning the Aurelia repository.

  • Building the entire Aurelia 2 monorepo.

  • Running tests in the browser and Node.js.

Setup

In order to build Aurelia, ensure that you have , v15.4.0 or higher, and npm@7.0.0 or higher installed.

Run the following commands to clone, install:

git clone https://github.com/aurelia/aurelia.git && cd aurelia
npm ci

packages

From the root level of the project, run npm run dev to start the development. This will:

  • build & watch the runtime package for rebuild

  • build & watch the runtime-html package for rebuild

  • build & watch the __testing__ package for rebuild

  • start a process to run all the tests with karma

Example scenarios:

  1. Fixing a repeater bug, so run all the repeater tests and rebuild repeater source code on change:

npm run dev -- --test repeater
  1. Fixing a router bug, so run all the router tests and rebuild router source code on change:

npm run dev -- --dev router --test router
  • The --dev (shortcut: -d) is to specify what additional package beside runtime & runtime-html packages should be rebuild on changes

  • The --test (shortcut: -t) is to specify what glob to search test files to run

This documentation will be expanded upon in the future.

packages-tooling

Similar to core packages, to develop/test any of the tooling packages, run npm run dev:tooling to start the development. This will

  • build & watch the kernel core package for rebuild

  • build & watch the plugin-conventions tooling package for rebuild

  • start a process to run all the tests with mocha

Example scenarios:

  1. Fixing a convention bug, so run all the plugin convention tests, and rebuild plugin-conventions tooling package on code change:

npm run dev -- --test plugin-conventions
# or
npm run dev -- --test conventions
  1. Fixing a webpack loader bug, sp run all the load tests and rebuild webpack loader code on change

npm run dev -- --dev webpack-loader --test loader
Git
Node.js