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

Provide es5 compatible luigi #53

Closed
kwiatekus opened this issue Sep 7, 2018 · 8 comments
Closed

Provide es5 compatible luigi #53

kwiatekus opened this issue Sep 7, 2018 · 8 comments
Labels
wontfix This will not be worked on
Milestone

Comments

@kwiatekus
Copy link
Contributor

Description

Provide es5 compatible versions for :

  • client - compile it manually and commit to the repo.
  • core - set up target version to es5

Reasons

There seem to be interest in having es5 compatible luigi (core and client)

@kwiatekus kwiatekus added this to the Sprint_Swinka_0 milestone Sep 7, 2018
@kwiatekus
Copy link
Contributor Author

@y-kkamil :

there's no need to change anything in core - apparently babel compiles code to es5 implicitly

@kwiatekus
Copy link
Contributor Author

@y-kkamil :

I have created UMD for client lib, as defined in https://github.com/umdjs/umd
which means that client will be available with node's require, regular import statement and also as a global object

@kwiatekus
Copy link
Contributor Author

#33

@kwiatekus kwiatekus modified the milestones: Sprint_Swinka_0, Sprint_Swinka_1 Sep 18, 2018
@y-kkamil
Copy link

  • added babel-polyfill to support es6+ features in core.
  • added polyfills.js file to enable support for some DOM functionalities we make use of in core (.prepend() method, onhashchange newURL/oldURL properties) that IE 11 lacks. (they are not covered by babel-polyfill)
  • not a perfect solution, though - every time one makes use of something that is not supported, he has to add the polyfill to polyfill.js

luigi-sample-angular related:

  • also, luigi-sample-angular won't work out-of-box. IE-relevant lines of code have to be uncommented in polyfills.ts file before running it. should we document that somehow?
  • even with all these polyfills in place app still crashes somehow with:
    Uncaught (in promise): TypeError: Unable to get property 'instance' of undefined or null reference
    seems to be an angular related problem

@y-kkamil
Copy link

this needs to be investigated further. how to support ie 11 with as less pain as possible ;)

@y-kkamil y-kkamil modified the milestones: Sprint_Swinka_1, Backlog_Swinka Sep 20, 2018
@y-kkamil y-kkamil removed their assignment Sep 20, 2018
@y-kkamil
Copy link

there's a closed PR, that might be worth checking with a basic solution:
#98

@stale
Copy link

stale bot commented Nov 19, 2018

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Nov 19, 2018
@stale
Copy link

stale bot commented Nov 26, 2018

This issue has been automatically closed due to the lack of recent activity.

@stale stale bot closed this as completed Nov 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants