Tripleslash references
See original GitHub issueTrying build my project after including the pipes throws an error: “Exported external package typings file cannot contain tripleslash references.”
The code is simple as:
import {TailPipe, HeadPipe} from 'angular-pipes';
@Component({
selector: 'page',
pipes: [TailPipe, HeadPipe],
directives: [BannerComponent, PageLinkDirective],
template: `{{list | head}}
<spand *ngFor="let item of list | tail">{{item}}</span>
`
})
export class Page extends BasePage {
list = [1,2,3];
}
I’m building with Angular2 rc.1, angular-pipes 1.6.0, node 6.0.0, typings 0.8.1
Removing the tripleslashes from angular-pipes/index.ts
solved it.
Issue Analytics
- State:
- Created 7 years ago
- Comments:16 (9 by maintainers)
Top Results From Across the Web
Documentation - Triple-Slash Directives - TypeScript
Triple -slash references instruct the compiler to include additional files in the compilation process. They also serve as a method to order the...
Read more >typescript-eslint/triple-slash-reference.md at main - GitHub
TypeScript's /// triple-slash references are a way to indicate that types from another module are available in a file. Use of triple-slash reference...
Read more >triple-slash-reference - TypeScript ESLint
TypeScript's /// triple-slash references are a way to indicate that types from another module are available in a file. Use of triple-slash reference...
Read more >When do I need a triple slash reference? - Stack Overflow
You need a triple slash reference in two scenarios: When you are referencing JavaScript type definitions e.g. definitions for node, jQuery, etc. for...
Read more >Triple slash directive | TypeScript Tutorial - YouTube
Why reference other files in our file? •.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m closing this, I found it in the doc of webpack:
http://webpack.github.io/docs/configuration.html#resolve-extensions
The
.ts
is first in your configuration.1.6.0
is not supporting RC.1. It will come for2.0.0
, it’s pushed on GitHub, I just have to do some more changes before I publish it on npm.