Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
This repository was archived by the owner on Aug 1, 2024. It is now read-only.

antony/sapper-ie

Open more actions menu

Repository files navigation

Sapper IE

IE and Windows Edge barely qualify as browsers, but they are able to render HTML/CSS and execute JS, in a form. These modifications to the language help incapable browsers render websites.

Status:

It Works!

  • IE11 - Fully working
  • Edge - Fully working

Changes from default Sapper

  1. Polyfils in template.html (via Polyfill.io):
  • default
  • fetch
  • Array.prototype.find
  • Object.values (not strictly necessary - but useful)
  1. Non-legacy (regular build) has rest spread so that Edge works (wow)
!legacy && babel({
    extensions: ['.js', '.mjs', '.html', '.svelte'],
    exclude: ['node_modules/@babel/**'],
    plugins: [
      '@babel/plugin-syntax-dynamic-import',
      '@babel/plugin-proposal-object-rest-spread'
    ]
  }),
  1. Special run mode to run the app via bable for easy local testing
npm run build:dev

Running

Don't expect this to work in IE/Edge in dev mode.

npm run build # has shimport hack for easier debugging
node __sapper__/build

About

Sapper working in IE11/Edge

Topics

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages

Morty Proxy This is a proxified and sanitized view of the page, visit original site.