question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Pipes could not be found with Ivy enabled

See original GitHub issue

This is an Ivy bug report.

I’m submitting a…


[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
[ ] Other... Please describe:

Current behavior

Event with the correct imports and declarations I get the following error

The pipe 'async' could not be found ("
    </div>

    <div class="progress-bar" [ERROR ->]*ngIf="isProgressBarVisible$ | async"></div>
</div>

"):

Expected behavior

It should compile

What is the motivation / use case for changing the behavior?

Just checking the compiler status

Environment


Angular version: 7.0.0-rc.1
 
For Tooling issues:
- Node version: NodeJS 10.12
- TypeScript version: 3.1.3

Others:
This is an *Ivy* bug report. I reported it, because the status page says pipes should work. Feel free to close this issue, if it's not the right time to submit bug tickets. 

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:3
  • Comments:36 (20 by maintainers)

github_iconTop GitHub Comments

13reactions
tiagoboeingcommented, Jan 20, 2019

I have same problem, and turned off ivy too. The problem is with pipes ERROR in : Template parse errors: The pipe 'date' could not be found....

For turn off ivy, open tsconfig.json and edit the key ivy to false.

"angularCompilerOptions": {
    "enableIvy": false
}
8reactions
alippaicommented, Oct 13, 2018

It’s failing for other reasons (first could not resolve foreign function declaration: app.module.ts forRoot, after fix Module not found: [object Object]).

Debug on Windows fails: HostResourceLoader: host(C:\Repositories\admin/C:/Repositories/admin/src/ts/components/dashboard/dashboard.component.html) returned a Promise

So I’ll leave this here, maybe it helps the Angular developers.

Read more comments on GitHub >

github_iconTop Results From Across the Web

The pipe ' ' could not be found - error after Angular upgrade
During the production build ( ng build --prod ) it removes the pipes due to tree shaking. Ivy is not fully compatible yet...
Read more >
Deprecated APIs and features
Sometimes, APIs and features become obsolete and need to be removed or replaced so that Angular can stay current with new best practices, ......
Read more >
The Angular Ivy guide for library authors
The Ivy Instruction Set which is the compilation output in directive and component rendering functions will not be finalised before Angular ...
Read more >
What Is Angular Ivy and Why Is It Awesome?
But unlike rewrites two and three, which you might not have even noticed ... you would need to refactor your code to be...
Read more >
All About Angular Engine Ivy in 5 mins
It is very advanced and offers advanced features that were not available ... They both are able to make Ivy capable of what...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found