[PR #425] [CLOSED] IE Support #2619

New issue

Closed

opened 2026-03-17 00:18:24 +03:00 by kerem · 0 comments

kerem commented

2026-03-17 00:18:24 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/hoppscotch/hoppscotch/pull/425
Author: @AndrewBastin
Created: 12/13/2019
Status: ❌ Closed

Base: master ← Head: feature/ie-support

📝 Commits (10+)

9d4b1fe Added build-ie script to package.json
d7c9d23 Added ora and rimraf as dev dependency
23fb8be Added IE build script content
0de31d4 Updated lockfile
3524b3f Added polyfills for compatibility with IE
96ec257 Merge remote-tracking branch 'upstream/master' into feat/ie_support
b2035bd Added babel and babel-core dev dependencies
04135c9 Updated build script to use npx while running babel
1520304 Merge branch 'master' into feature/ie-support
0ac9772 Added IE polyfill for CSS variables

📊 Changes

5 files changed (+1713 additions, -43 deletions)

View changed files

➕ build-ie.js (+55 -0)
📝 nuxt.config.js (+8 -0)
📝 package-lock.json (+1063 -42)
📝 package.json (+6 -1)
➕ static/polyfill-ie-css.js (+581 -0)

📄 Description

NOTE : This is a draft PR, implementation hasn't reached a stable standard, the PR is opened as a notification of ongoing work, as a place to discuss, and as an invitation to help make this feature stable

This PR intends to introduce IE (11) support to Postwoman.

Implemented So Far

Basic IE functionality

IE functionality is implemented by transpiling the generated Nuxt JS scripts into IE11 compatible ES5 code using Babel. This transpilation can be done by running the newly added command npm run build-ie. The generated dist folder will be IE compatible (to the extent that is implemented).

The site runs (with styling issues) on IE. Basic functionality (running REST, WebSocket and GraphQL requests) work without any issues (as far as I have tested, which isn't a lot). Missing modern JS features are patched into the site using polyfills from polyfill.io.

What's left to be done

Well, the styles are pretty broken, pretty sure its due the SCSS stuff and modern CSS features we use like media queries and ~~CSS variables~~ (added polyfill for variables in 0ac9772).
Thorough testing has to be done to check whether we missed something in IE or if we broke something in the other browsers.
Improve the build script ? (@jamesgeorge007, this might be something right up your ballpark)

We would love your help for implementing making this feature possible.

Happy Hacking!!!! 👨‍💻 👩‍💻 ❤️

This PR fixes #386

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/hoppscotch/hoppscotch/pull/425 **Author:** [@AndrewBastin](https://github.com/AndrewBastin) **Created:** 12/13/2019 **Status:** ❌ Closed **Base:** `master` ← **Head:** `feature/ie-support` --- ### 📝 Commits (10+) - [`9d4b1fe`](https://github.com/hoppscotch/hoppscotch/commit/9d4b1fe5a1ac7e1a816de6d2cfd3200e37f0dbef) Added build-ie script to package.json - [`d7c9d23`](https://github.com/hoppscotch/hoppscotch/commit/d7c9d236244957b5183fd3a17d5622d955d6fc92) Added ora and rimraf as dev dependency - [`23fb8be`](https://github.com/hoppscotch/hoppscotch/commit/23fb8be328d15f4003602b154a0fcf06782502b3) Added IE build script content - [`0de31d4`](https://github.com/hoppscotch/hoppscotch/commit/0de31d44d7503c59b72ed44b1d914a7b39d08666) Updated lockfile - [`3524b3f`](https://github.com/hoppscotch/hoppscotch/commit/3524b3fca3a1b71569d2e32a9afed1c2bca5c5fe) Added polyfills for compatibility with IE - [`96ec257`](https://github.com/hoppscotch/hoppscotch/commit/96ec2570ed2bba421cf0d5391df32fe05754f908) Merge remote-tracking branch 'upstream/master' into feat/ie_support - [`b2035bd`](https://github.com/hoppscotch/hoppscotch/commit/b2035bdc9507e12af81eaa11d4a15adf3851827c) Added babel and babel-core dev dependencies - [`04135c9`](https://github.com/hoppscotch/hoppscotch/commit/04135c9e102a3bdd0e4cf840d7ff649807859124) Updated build script to use npx while running babel - [`1520304`](https://github.com/hoppscotch/hoppscotch/commit/15203049c6ed434e4eadb529424bafb1c1bed59c) Merge branch 'master' into feature/ie-support - [`0ac9772`](https://github.com/hoppscotch/hoppscotch/commit/0ac97727c814d78ef6def1db6584ba7f94e6af88) Added IE polyfill for CSS variables ### 📊 Changes **5 files changed** (+1713 additions, -43 deletions) <details> <summary>View changed files</summary> ➕ `build-ie.js` (+55 -0) 📝 `nuxt.config.js` (+8 -0) 📝 `package-lock.json` (+1063 -42) 📝 `package.json` (+6 -1) ➕ `static/polyfill-ie-css.js` (+581 -0) </details> ### 📄 Description ***NOTE : This is a draft PR, implementation hasn't reached a stable standard, the PR is opened as a notification of ongoing work, as a place to discuss, and as an invitation to help make this feature stable*** This PR intends to introduce IE (11) support to Postwoman. # Implemented So Far ### Basic IE functionality IE functionality is implemented by transpiling the generated Nuxt JS scripts into IE11 compatible ES5 code using [Babel](https://babeljs.io). This transpilation can be done by running the newly added command `npm run build-ie`. The generated `dist` folder will be IE compatible (to the extent that is implemented). The site runs (with styling issues) on IE. Basic functionality (running REST, WebSocket and GraphQL requests) work without any issues (as far as I have tested, which isn't a lot). Missing modern JS features are patched into the site using polyfills from [polyfill.io](https://polyfill.io). # What's left to be done - Well, the styles are pretty broken, pretty sure its due the SCSS stuff and modern CSS features we use like media queries and ~~CSS variables~~ (added polyfill for variables in 0ac9772). - Thorough testing has to be done to check whether we missed something in IE or if we broke something in the other browsers. - Improve the build script ? (@jamesgeorge007, this might be something right up your ballpark) We would love your help for implementing making this feature possible. Happy Hacking!!!! 👨‍💻 👩‍💻 ❤️ This PR fixes #386 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>