MDsveX: npx sapper export results in 404 for index.svx

Hi again,

Using npx sapper export results in a build that 404’s most pages. Does sapper-mdsvex support exporting in this way? The goal is to export on a branch for github pages.

About this issue

Original URL
State: open
Created 4 years ago
Comments: 18 (5 by maintainers)

Most upvoted comments

I’ll take a look at this as soon as I can. Pretty busy right now sadly. Not entirely sure what is going on.

pngwn on Sep 22, 2020

You’re the best @pngwn! And nicely done @jamesb93!

betweenvenus on Oct 30, 2020

@pngwn Here’s mine:

npx: installed 1 in 1.416s

  System:
    OS: Windows 10 10.0.18363
    CPU: (4) x64 Intel(R) Core(TM) i5-7600 CPU @ 3.50GHz
    Memory: 3.22 GB / 15.96 GB
  Binaries:
    Node: 12.18.4 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.5 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.6 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.18362.449.0)
    Internet Explorer: 11.0.18362.1
  npmPackages:
    rollup: ^2.23.1 => 2.23.1
    sapper: ^0.28.0 => 0.28.0
    svelte: ^3.0.0 => 3.24.1

betweenvenus on Sep 22, 2020

And same problem after runing yarn upgade sevlte sapper:


  System:
    OS: macOS Mojave 10.14.6
    CPU: (8) x64 Intel(R) Core(TM) i7-4980HQ CPU @ 2.80GHz
    Memory: 1.67 GB / 16.00 GB
    Shell: 3.1.2 - /usr/local/bin/fish
  Binaries:
    Node: 14.11.0 - /usr/local/bin/node
    Yarn: 1.22.5 - /usr/local/bin/yarn
    npm: 6.14.8 - /usr/local/bin/npm
  Browsers:
    Edge: 85.0.564.41
    Firefox: 80.0.1
    Safari: 13.1.2
  npmPackages:
    rollup: ^2.23.1 => 2.23.1 
    sapper: ^0.28.0 => 0.28.8 
    svelte: ^3.0.0 => 3.26.0

jamesb93 on Sep 22, 2020

hi @betweenvenus I’m on macOS 10.14.6. I have Windows on another machine that I’d be happy to help debug with though if that helps @pngwn.

jamesb93 on Sep 22, 2020