-
Notifications
You must be signed in to change notification settings - Fork 138
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
Detect type="module" #450
Detect type="module" #450
Conversation
This seems like a viable quick fix. What I'd like to aim for is modernizing ical.js to use es6 modules instead of trying to cram everything onto a global variable, but still keep the Can you add a comment inside the if block what this is for? Also, you may need to adjust the jshint and istanbul comments before so they apply to the correct blocks. |
390a148
to
04236c7
Compare
👍 Godspeed! Looking forward to those changes.
Left a comment.
Adjusted the comments. |
bump. |
Update: I noticed that when executing So in fb1e238, I'm now making sure that |
👋🏼 Hey, this PR has now been open for half a year. I prefer to use the actual ical.js in my application and not continue to rely on my personal fork. So can you please come to a decision about merging this PR? Thanks! Best, |
I appreciate the work you've done here, even if the timeline for responding may not suggest so. I'm going to add your case to #470 and get it fixed there, let me know if you can think of a case where window is not defined but HTMLScriptElement is. |
Fixes #449
This is merely an attempt to fix the above mentioned issue. The problem with this fix this that so far it only detects if the Javascript modules feature is available in the browser. However, a developer could add a regular
<script>
tag in a browser that supports modules. Then this statement would still run.I don't see it much of a problem though, as the added statement runs in addition to the statements below, fixing it for the problems described in the linked issue #449