-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Universal server side rendering #764
Conversation
Doesn't typescript handle the |
If you look at the transpiled code https://github.com/swimlane/ngx-datatable/blob/master/release/index.js#L3809 There are dozens of mentions of MouseEvent and KeyboardEvent, all these are not defined. This seems to be a common problem with angular components as I've found other have faced similar problems. leovo2708/ng2-dropdown-treeview#23 |
What's the status on this PR? We are looking for the same change. |
Merged. |
@stupiduglyfool This has now been merged into version 9.3.0 but on the universal side of things I'm still getting the following error:
Any suggestions? |
@stupiduglyfool and @amcdnl I've found a solution. I'll issue a bug and a pull request later today. |
Universal server side rendering
Using 9.3.0, still experience the same issue just like @rsparrow . Using with @angular/service-worker |
@rsparrow I think all |
@mattma My fixes didn't get packaged into a release until 9.3.1... |
by updating to 9.3.1, it works as expected. Still waiting on I am using Is there a timeline on when the feature will drop? Thinking of switching to Angular CDK table module. i will be a quick bit of code refactor that I hope I can avoid with the future release of the library. |
What kind of change does this PR introduce? (check one with "x")
What is the current behavior? (You can also link to an open issue here)
Any references to Window, Document, MouseEvent, KeyboardEvent cause errors.
#173
What is the new behavior?
Similar to the comment here..
#173 (comment)
I've gone through all references and attempted to create a suitable workaround when the mentioned references are used.
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:
Open to suggestions if anyone can suggest better approaches to my workarounds.