Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running Sentio in Angular CLI throws runtime error in prod mode #30

Open
lu-c opened this issue Nov 18, 2019 · 2 comments
Open

Running Sentio in Angular CLI throws runtime error in prod mode #30

lu-c opened this issue Nov 18, 2019 · 2 comments

Comments

@lu-c
Copy link

lu-c commented Nov 18, 2019

I'm experiencing this issue where I'm trying to include sentio into an angular-cli project. When I run the project in dev mode, everything works. When I run in prod mode, sentio breaks. I've tracked the problem down to the optimization config option - if that flag is set to false, sentio will work.

This is the error you see at runtime:

    at lY (time.js.pre-build-optimizer.js:30)
    at oY (time.js.pre-build-optimizer.js:134)
    at eI (timeline.js.pre-build-optimizer.js:79)
    at new t (timeline.directive.js.pre-build-optimizer.js:28)
    at Vl (core.js.pre-build-optimizer.js:22140)
    at Hl (core.js.pre-build-optimizer.js:22019)
    at vo (core.js.pre-build-optimizer.js:23245)

Clicking on the first stacktrace link opens up this:
Screen Shot 2019-11-18 at 4 14 10 PM
(Error highlights on line 30)

My package.json looks like this:

"devDependencies": {
    "@asymmetrik/sentio": "5",
    "@asymmetrik/ngx-sentio": "5",
    "d3": "5",
    "@types/d3": "5"
}

Any thoughts?

@reblace
Copy link
Contributor

reblace commented Nov 19, 2019

I doubt this is your issue, but @asymmetrik/ngx-sentio@6 is for Angular 8. I get a different error than what you're reporting when I run v5 with Angular 8

@kittrCZ
Copy link

kittrCZ commented Feb 17, 2020

had the same problem.
Solved be defining the "version": "5.7.0" in the package.json. No time for digging deeper now, but there seems to be some problem with the latest version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants