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

Drop IE11 support and remove unmaintained depends #277

Merged
merged 1 commit into from Sep 25, 2023
Merged

Conversation

BryanQuigley
Copy link
Collaborator

@BryanQuigley BryanQuigley commented Aug 17, 2023

Aside from letting us drop the legacy build it also let's us drop the jquery-deparam dependency replacing with built-in urlSearchParams

Confirmed this seems to work just fine - just not on IE11.

@BryanQuigley BryanQuigley marked this pull request as ready for review August 19, 2023 06:28
Aside from letting us drop the legacy build it also
let's us drop the jquery-deparam dependency replacing
with built-in urlSearchParams
@BryanQuigley
Copy link
Collaborator Author

This is a prerequisite for further improvements (or removal) of jquery. Confirmed through recent stats that IE is easily less than .1% (For reference Edge is at 6%)

@@ -1,5 +1,4 @@
<!-- general behavior -->
<script type="module" src="{{ site.baseurl }}/scripts/dist/modern/index.js"></script>
<script nomodule src="{{ site.baseurl }}/scripts/dist/legacy/index.js"></script>
<script type="module" src="{{ site.baseurl }}/scripts/dist/index.js"></script>
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The package.json still uses a named target. I would assume that npm run build still outputs the compiled index.js file to the modern directory, doesn't it? If not, feel free to disregard.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope, it doesn't - and this was odd to me as well.

@timwis
Copy link
Owner

timwis commented Sep 25, 2023

Hey Bryan, sorry for the delay. I'm happy with this change in principle - just left one question for you to confirm, then happy for you to merge when ready.

@BryanQuigley BryanQuigley merged commit 071ed3c into main Sep 25, 2023
1 check passed
@BryanQuigley BryanQuigley deleted the legacy branch September 25, 2023 21:36
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

Successfully merging this pull request may close these issues.

None yet

2 participants