Write Component-Relative URLs to component templates and style files
Our components often refer to external template and style files.
We identify those files with a URL in the
styleUrls properties of the
as seen here:
By default, we must specify the full path back to the application root. We call this an absolute path because it is absolute with respect to the application root.
There are two problems with an absolute path:
We have to remember the full path back to the application root.
We have to update the URL when we move the component around in the application files structure.
It would be much easier to write and maintain our application components if we could specify template and style locations relative to their component class file.
We can if we build our application as
commonjs modules and load those modules
with a suitable package loader such as
Learn why below.
The Angular CLI uses these technologies and defaults to the component-relative path approach described here. CLI users can skip this chapter or read on to understand how it works.
Our goal is to specify template and style URLs relative to their component class files, hence the term component-relative path.
The key to success is following a convention that puts related component files in well-known locations.
We recommend keeping component template and component-specific style files as siblings of their
companion component class files.
Here we see the three files for
SomeComponent sitting next to each other in the
We'll have more files and folders — and greater folder depth — as our application grows. We'll be fine as long as the component files travel together as the inseparable siblings they are.
Set the moduleId
Having adopted this file structure convention, we can specify locations of the template and style files
relative to the component class file simply by setting the
moduleId property of the
@Component metadata like this
We strip the
src/app/ base path from the
styleUrls and replace it with
The result looks like this:
Webpack users may prefer an alternative approach.
We can see the
Appendix: why component-relative is not the default
A component-relative path is obviously superior to an absolute path.
Why did Angular default to the absolute path?
Why do we have to set the
moduleId? Why can't Angular set it?
First, let's look at what happens if we use a relative path and omit the
EXCEPTION: Failed to load some.component.html
Angular can't find the file so it throws an error.
Why can't Angular calculate the template and style URLs from the component file's location?
Because the location of the component can't be determined without the developer's help. Angular apps can be loaded in many ways: from individual files, from SystemJS packages, or from CommonJS packages, to name a few. We might generate modules in any of several formats. We might not be writing modular code at all!
With this diversity of packaging and module load strategies, it's not possible for Angular to know with certainty where these files reside at runtime.
The only location Angular can be sure of is the URL of the
index.html home page, the application root.
So by default it resolves template and style paths relative to the URL of
That's why we previously wrote our file URLs with an
app/ base path prefix.
But if we follow the recommended guidelines and we write modules in
and we use a module loader that plays nice,
then we — the developers of the application —
know that the semi-global
module.id variable is available and contains
the absolute URL of the component class module file.
That knowledge enables us to tell Angular where the component file is
by setting the
Webpack: load templates and styles
Webpack developers have an alternative to
They can load templates and styles at runtime by adding
./ at the beginning of the
properties that reference *component-relative URLS.
Webpack will do a
require behind the scenes to load the templates and styles. Read more here.
See the Introduction to Webpack.