Comments (3)
I agree. Previously, baseUrl
was added by default when generating an Angular application, so there was no issue, but when transitioning to Vite, Angular developers also simplified the TypeScript configuration by removing baseUrl
. Apparently, I forgot to add it during the code migration.
In general, simply adding baseUrl: "."
as it was before should suffice, but I've also been informed (#144) that some features stopped working with the release of Angular 17.3, and I'm working on that.
Nevertheless, you're right, paths should be relative. I have already fixed this in a newer version that I'm currently working on, so it should be fixed when I release it.
from ng-doc.
By the way, the baseUrl
is not specified by default when generating an Angular application, and is also not added by @ng-doc/add
. If the developer did not explicitly specify it, a TypeScript error will occur when trying to build or serve the application.
from ng-doc.
I think this issue was fixed by the latest releases, feel free to reopen it if it's still an issue
from ng-doc.
Related Issues (20)
- [Bug] Playground Feature Not Working HOT 2
- Amazing Work HOT 1
- [Bug] `@ng-doc/builder:dev-server` Schema Validation Error When the `ngDoc` Propertiy is Provided HOT 15
- [Feature] Support `.js` Version of Ng Doc Configuration File HOT 4
- [Feature] Use Dark Theme by Default HOT 7
- [Docs] Update ng-doc path in docs HOT 2
- [Feature] Remove Google Fonts HOT 4
- [Bug] ng-doc.routing.ts incorrect generated import HOT 10
- [Bug] input aliasing decorator selector not rendered correctly HOT 4
- [Feature] Support template variables for inputs HOT 11
- [Bug] hidden: true in NgDocPage-Config does not avoid displaying a component in the navigation. HOT 7
- [Bug] Table of contents link does not work properly with basehref HOT 4
- [Bug] Unable to leverage Keywords to create custom links in a reusable macro template HOT 8
- [Feature] Unable to leverage Custom Angular Components in the Markdown file HOT 5
- Support for Mermaid HOT 7
- [Bug] Unable to build docs when Playground refers components from angular library HOT 3
- [Bug] Extra /docs is introduced in the home icon of the breadcrumb during configuration of NgDoc route prefix HOT 4
- [Bug] Unable to display demo details of the components from angular library HOT 3
- [Query] Is it possible to import macros from angular library? HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ng-doc.