I also prefer indented, but the goal was to not change any rules at all (where possible). New rules should be voted on via the PR system on the eslint-config project.

oh interesting, it's indented the code and not the comments. Is there an eslint rule to configure this? I don't use comments.

Agreed. I can't even figure out how this is supposed to look.

This is the result of simply tightening all the warnings to errors, and then running auto-fix, not adding any more rules. As to what rule causes/controls this change, I don't know. Any ideas?

The "correct" format for a switch statement is un-indented, so I've gone with that with the view to vote on our preferred indentation format, since both styles were present in the codebase, from what I remember.

This is all the cleanup required from tightening of the lint rules.

It currently depends on an unmerged branch of the eslint project, so that should be merged prior to this being merged, if approved.

Before submitting the PR, please make sure you do the following

• [ ] It's really useful if your PR relates to an outstanding issue, so please reference it in your PR, or create an explanatory one for discussion. In many cases, features are absent for a reason.
• [ ] This message body should clearly illustrate what problems it solves. If there are related issues, remember to reference them.
• [ ] Ideally, include a test that fails without this PR but passes with it. PRs will only be merged once they pass CI. (Remember to npm run lint!)

Tests

• [ ] Run the tests with npm test or yarn test)

This issue is 3 years old. To get help with goto, come and [https://svelte.dev/chat](chat to us)

When I get a minute I'll update this to use the new lib that I use in my other modules. That should fix these errors, I suspect facebook made some updates which have broken their SDK for this use case, which they seem prone to doing.

This is related to https://github.com/sveltejs/sapper/issues/1346 and related to the RFC I'm working on. I think adamb on discord is also doing something along these lines.

I'll try to publish the RFC as soon as possible to try to bring all efforts into a single place.

Might be worth mentioning that Rollup is able to tree-shake more optimally, resulting in a smaller bundle size.

Whilst cancellation of preloading might be desirable, this has nothing to do with Axios - Sapper uses fetch.

You've suggested that navigating to a route whilst preloading is in progress causes 'conflict'. However you haven't specified what this conflict is. Could you update the ticket to provide a specfiic scenario you're trying to prevent?

Is your feature request related to a problem? Please describe. I'm using vite to build a site with Svelte, using Svite. It works well! The only missing link for me is supporting older browsers. It'd be ideal to have a way to run babel over the code, just before minification.

Describe the solution you'd like If I manually modify the rollup config builder to inject the @rollup/plugin-babel plugin, it works well. Ideally I'd like a way to do that via configuration - it's already possible to add plugins before other plugins, but it would be good to have more fine-grained control over their insertion order in the config.

Describe alternatives you've considered Not supporting around 5% of my userbase, unfortunately.

I'd be happy to accept a PR for this :)

Did you try

fb.track('Purchase', { currency, value })

As an update on this, I've started working to update Svelte to follow its own linting rules. There is some mutation of node built-ins going on which are also dependent on run-order, so it will take a bit of untangling of that first. I'll open a draft PR when I'm able.

At what point do we just remove this error entirely?

It's been a long, long time since 0.10 and we don't have these sorts of protections around other breaking changes.

Just coming back to this issue since my use-case has required changes to the way I do this.

I'd solved for the original case with some complex afterUpdate logic and memoisation, but now I've moved the inner component to a fully store+context based model, it isn't reactive in the way it used to be. I'm now 2-3 hours deep re-solving the same problem.

No matter what sort of optimal rendering scenario we're gaining here, the developer experience is extremely poor. I think onEnter or onExit (with whatever naming is preferred) would be a great solution. The PR at https://github.com/sveltejs/sapper/pull/1047 might make a nice starter.

If a PR like this were to exist, would there be any resistance?

If you're deploying your app outside your machine, make sure that you include production dependencies (required by) `server.js` by installing all dependencies from `package.json`:

npm --production

  as well as including your `static` directory and it's contents.

not sure if we should also include npm prune, but I figure that we're not an npm tutorial.

> Note that the default behaviour of the service worker is to cache all assets from the static directory, so if you have more than 50mb of files here, you will start to exceed the cache limit for service-workers in some browsers, which can cause the service worker to stop loading. In this instance, it is advisable to customise what files are cached by editing the service-worker yourself.

This gets asked a lot. I'm not quite sure why Svelte has this additional restriction over normal TypeScript, but it'd be good to mention it up front

@julienchazal the question/help template says "don't ask support questions on github!"

Not sure the comment is necessary?

Hello,

Is it possible to import svelte component using dynamic path like this :

https://svelte.dev/repl/10e44f4140e4483e87f30ef163ba2164?version=3.24.1

i'm not sure if it's even possible with ES6, or maybe it depends on rollup/webpack config ? i've tried same thing using sapper with no luck (the idea behind is to make a custom "storybookjs" using Figma API 👍

Thx for your help !

@julienchazal it doesn't mean it should be a github issue, sorry. Please try rephrasing your question and persisting with discord, asking on stackoverflow, or otherwise.

Fixes https://github.com/sveltejs/sapper/issues/1263

Before submitting the PR, please make sure you do the following

• [ ] It's really useful if your PR relates to an outstanding issue, so please reference it in your PR, or create an explanatory one for discussion. In many cases features are absent for a reason.
• [ ] This message body should clearly illustrate what problems it solves. If there are related issues, remember to reference them.

Did you @dmgolembiowski @tippexx get any further with diagnosing this?

Without looking into this too deeply, have you tried calling your routes index.html.svelte and then trying to visit index.html?

@zw5 can you try this on node v12 please and see if you have a better result?

Fixes https://github.com/sveltejs/sapper/issues/1328

Before submitting the PR, please make sure you do the following

• [ ] It's really useful if your PR relates to an outstanding issue, so please reference it in your PR, or create an explanatory one for discussion. In many cases features are absent for a reason.
• [ ] This message body should clearly illustrate what problems it solves. If there are related issues, remember to reference them.
• [ ] Ideally, include a test that fails without this PR but passes with it. PRs will only be merged once they pass CI. (Remember to npm run lint!)

Tests

• [ ] Run the tests tests with npm test or yarn test)

I created a template sapper project, updated and installed packages (ncu -u && npm i). Then I added any 40-50mb images to the static directory. This causes the site to hang after updating. DevTools -> Application -> Service Workers says Status: trying to install.

An example project with a problem (there are several images from Wikipedia in the static directory): https://github.com/ljonya/sapper-app

The problem appears at first run (npm run dev), sometimes you need to update something in .svelte files, sometimes you need Unregister already installed Service Worker in DevTools.

Logs Logs are empty.

To Reproduce

1. Run the example: https://github.com/ljonya/sapper-app
2. In DevTools -> Application -> Service Workers: Unregister already installed Service Worker.
3. Refresh the page in Chromium and possibly update, for example, index.svelte.

Information about Sapper Installation:

• Chromium 84.0.4147.89 (Official build), snap (64 bit)
• Kubuntu 20.04 64 bit
• Sapper version 0.27.16
• Svelte version 3.24.0
• Application uses Rollup

I think I prefer sapper-noscroll which makes it clear that it's a Sapper specific thing. 'noscroll' feels like an built-in attribute.

Bumps acorn from 6.1.1 to 6.4.1. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/acornjs/acorn/commit/9a2e9b6678e243d66846b91179d650d28453e70c"><code>9a2e9b6</code></a> Mark version 6.4.1</li> <li><a href="https://github.com/acornjs/acorn/commit/90a9548ea0ce351b54f956e2c4ed27cca9631284"><code>90a9548</code></a> More rigorously check surrogate pairs in regexp validator</li> <li><a href="https://github.com/acornjs/acorn/commit/df0cf1a3e2b1a51a26c14984dc0f5412b7151b10"><code>df0cf1a</code></a> Mark version 6.4.0</li> <li><a href="https://github.com/acornjs/acorn/commit/53034126864b492da4e278628bb972cb2a9313d4"><code>5303412</code></a> Also export Parser via Parser.acorn</li> <li><a href="https://github.com/acornjs/acorn/commit/efe273e70123449a458157dbf578afaf109a49ab"><code>efe273e</code></a> give token types and etc to plugins</li> <li><a href="https://github.com/acornjs/acorn/commit/ac6decb94a3aa4eee99230fdaf5883dfaafe8479"><code>ac6decb</code></a> Mark version 6.3.0</li> <li><a href="https://github.com/acornjs/acorn/commit/7e9817d17639d95cc6dbacfde734a0626b2a7dea"><code>7e9817d</code></a> Allow sourceType: module even with ecmaVersion < 6</li> <li><a href="https://github.com/acornjs/acorn/commit/e2b8cc087386eccc2ad6fd4a02b4257833557cb3"><code>e2b8cc0</code></a> Fix broken parsing of new expressions when allowReserved=="never"</li> <li><a href="https://github.com/acornjs/acorn/commit/1555c528855b10320ce98b4154906d7898c92990"><code>1555c52</code></a> Update acorn.d.ts</li> <li><a href="https://github.com/acornjs/acorn/commit/77c20fa2c2f490e646b67e6a0ff7e75fb54ab6c8"><code>77c20fa</code></a> Mark version 6.2.1</li> <li>Additional commits viewable in <a href="https://github.com/acornjs/acorn/compare/6.1.1...6.4.1">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps mixin-deep from 1.3.1 to 1.3.2. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jonschlinkert/mixin-deep/commit/754f0c20e1bc13ea5a21a64fbc7d6ba5f7b359b9"><code>754f0c2</code></a> 1.3.2</li> <li><a href="https://github.com/jonschlinkert/mixin-deep/commit/90ee1fab375fccfd9b926df718243339b4976d50"><code>90ee1fa</code></a> ensure keys are valid when mixing in values</li> <li>See full diff in <a href="https://github.com/jonschlinkert/mixin-deep/compare/1.3.1...1.3.2">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~doowb">doowb</a>, a new releaser for mixin-deep since your current version.</p> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps lodash from 4.17.15 to 4.17.19. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/lodash/lodash/releases">lodash's releases</a>.</em></p> <blockquote> <h2>4.17.16</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lodash/lodash/commit/d7fbc52ee0466a6d248f047b5d5c3e6d1e099056"><code>d7fbc52</code></a> Bump to v4.17.19</li> <li><a href="https://github.com/lodash/lodash/commit/2e1c0f22f425e9c013815b2cd7c2ebd51f49a8d6"><code>2e1c0f2</code></a> Add npm-package</li> <li><a href="https://github.com/lodash/lodash/commit/1b6c282299f4e0271f932b466c67f0f822aa308e"><code>1b6c282</code></a> Bump to v4.17.18</li> <li><a href="https://github.com/lodash/lodash/commit/a370ac81408de2da77a82b3c4b61a01a3b9c2fac"><code>a370ac8</code></a> Bump to v4.17.17</li> <li><a href="https://github.com/lodash/lodash/commit/1144918f3578a84fcc4986da9b806e63a6175cbb"><code>1144918</code></a> Rebuild lodash and docs</li> <li><a href="https://github.com/lodash/lodash/commit/3a3b0fd339c2109563f7e8167dc95265ed82ef3e"><code>3a3b0fd</code></a> Bump to v4.17.16</li> <li><a href="https://github.com/lodash/lodash/commit/c84fe82760fb2d3e03a63379b297a1cc1a2fce12"><code>c84fe82</code></a> fix(zipObjectDeep): prototype pollution (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4759">#4759</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/e7b28ea6cb17b4ca021e7c9d66218c8c89782f32"><code>e7b28ea</code></a> Sanitize sourceURL so it cannot affect evaled code (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4518">#4518</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/0cec225778d4ac26c2bac95031ecc92a94f08bbb"><code>0cec225</code></a> Fix lodash.isEqual for circular references (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4320">#4320</a>) (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4515">#4515</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/94c3a8133cb4fcdb50db72b4fd14dd884b195cd5"><code>94c3a81</code></a> Document matches* shorthands for over* methods (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4510">#4510</a>) (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4514">#4514</a>)</li> <li>Additional commits viewable in <a href="https://github.com/lodash/lodash/compare/4.17.15...4.17.19">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~mathias">mathias</a>, a new releaser for lodash since your current version.</p> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

The unflatten function contains a prototype pollution vulnerability. I've added a test and fix.

This fixes #5 .

Flatley has prototype pollution vulnerablity and it may lead to logic vulnerability in application

var unflatten = require('flatley').unflatten
 
unflatten({
    '__proto__.polluted': true
})

console.log(polluted);

Are you installing it with --save-dev? It's essential that dependencies in Svelte are installed as devDependencies.

On Wed, 5 Aug 2020 at 20:42, Eli Albert [email protected] wrote:

it's definitely something to do with the build, it is sufficient to copy the svelte component into my app directly for this to start working.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/beyonk-adventures/svelte-carousel/issues/22#issuecomment-669449917, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABVORITAMPNURS2BRDKBXDR7GY37ANCNFSM4MHNWGEQ .

--

ꜽ . antony jones . http://www.enzy.org

@sdwvit it is the preference of the maintainers to handle support questions on discord, and bugs / feature requests on github issues. This is stated very clearly in the github issue template, and if people ignore it, their issues will be closed with this exact response.

If I understand this correctly - if you control the markup of the child component, you can easily add an action to it which is passed as a prop, so this doesn't really change anything other than adding API surface for something which, should the author of the child/third-party component wish, they could expose an API for anyway.

Describe the bug I have this code:

<script>
  let value = "0";

  function set() {
    value = "";
  }
</script>

<div>
  <input {value} on:input={set} />
</div>

It's supposed to clear input each time when user tries to type something. It actually clears input for the first time, but then it stops clearing and user becomes able to type everything he wants.

Logs No logs were emitted :smile:

To Reproduce REPL: https://svelte.dev/repl/7ae87bbae9c6470cabab36112f7fc706?version=3.24.0

Expected behavior Input must be cleared each time user types something.

Severity It's kinda annoying. :smile:

So to clarify. The set is working without issue. You can see this by console.loging the actual value. The view value of a field should be controlled using javascript, as is done above. This also updates the reactive binding so can be used to control both actual value and view value.

This isn't a bug, this is a known feature of how view values work - I know because I raised it myself before :)

Have automated releases been considered for svelte and sveltejs/*? It could potentially save developers a lot of time tracking down issues for which there's already been a merged, but not released, fix.

Hi @dnl-brnr

This seems like something you should ask in discord rather than as a github issue.

We have a changelog file which is dilligently updated. I'm not sure how automated releases will help this, but please feel free to come and discuss on discord.

As an aside, these files should be ignored by gitignore, so for people building and deploying from CI it shouldn't be an issue.

However. I'm not sure I agree with the basis of this PR. Maintaining yet another filter of files dumped all over the filesystem by some specific OS is just painful.

It might be better to understand the root cause of the DS_Store issue.

I've added the default value into where it is used, I'd probably recommend this approach for the other styles since right now you have to specify all of them if you want to change just one.

I've also removed a spurious colon on the final stop, as I think it was accidental?

I figured it out!

I was using node v14 as I've been upgrading a bunch of my projects. I dropped to v12 and it works absolutely fine.

I hope I haven't wasted anyone's time. Is it worth adding some messaging if you try to install on an (I assume) unsupported node version?

This is a fix for #481

Closing for now as it's stale. We can rebase+re-open with tests if this is still required

I want to create a web component using svelte. To create a web component it's necessary to include the svelte tag option

<svelte:options tag="{"my-custom-component}"></svelte:options>

It creates a custom component with that name but doesn't work properly because we have to provide this tag for all the child components as well! I added it to all the child components but it still doesn't work, turns out I use third party libraries and I don't know any way to have that option there!

Is there a way to create custom component with svelte which includes third party libraries?

Hi @Manzurkds

Please use discord for support questions.

Describe the bug When loading the svelte.dev site i get welcomed by an 500 error

Logs

SCRIPT1028: SCRIPT1028: Expected identifier, string or number
5258fa1b-3a9e-41ac-bc74-186716ab20e3 (1,64086)

0: Unable to get property 'R' of undefined or null reference 
app.bbeb5782.js (1,21620)

To Reproduce first time load, constantly happening; no idea how to reproduce

Expected behavior the site loads successfully

system Information

• Your browser and the version: (e.x. Chrome 52.1, Firefox 48.0, IE 10) Microsoft Edge 44.19041.1.0
• Your operating system: (e.x. OS X 10, Ubuntu Linux 19.10, Windows XP, etc) Windows 10 v2004

Severity Was going to check out svelte for the first time and then cant even get on the site

You're using an out of date, unmaintained/unsupported version of Edge which we don't support (as the site is not transpiled). Please try an alternate browser such as Chrome, or a more recent version of Edge.

Isn't this a job for the Svelte compiler rather than this template?

Closing this as I think the template should allow the user to define their own linting, testing, and other tools, as this is very developer centric (or set by company policy).

There are a lot of other templates out there which go a step further, so it's a matter of just choosing one with a combination of tools which suit you.

What do you think about the linter configuration in the template? For example for eslint and prettier. Using a template, I would not want to have a cognitive load when installing plugins for linter etc

Fixes https://github.com/sveltejs/template/issues/64

I think aliasing is the only way this would work, as demonstrated above.

if you think Svelte should be doing something it is not (which other tools are), however, please feel free to comment and we can re-open.

Describe the bug If you use the Svelte Template with Rollup using Yarn Workspaces and try to start the website it doesn't work and shows the error main.js:8 Uncaught ReferenceError: internal is not defined

Logs (Rollup Logs)

(!) Unresolved dependencies
https://rollupjs.org/guide/en/#warning-treating-module-as-external-dependency
svelte/internal (imported by src\App.svelte)
(!) Missing global variable name
Use output.globals to specify browser global variable names corresponding to external modules
svelte/internal (guessing 'internal')

To Reproduce I set up yarn workspaces and used degit to initialize my Svelte frontend. I ran yarn install in the project root

Occasionally, this won't be possible, and that's fine – we still appreciate you raising the issue. But please understand that Svelte is run by unpaid volunteers in their free time, and issues that follow these instructions will get fixed faster.

Expected behavior Svelte / Rollup should be able to resolve all it's dependencies with Yarn Workspaces just like other tools do

Information about your Svelte project:

• Tested in Chrome Canary (80.0.3948.0)

• Windows 10

• Svelte 3.12.1

• Rollup

Severity Not that severe just pretty annoying to not be able to use svelte in such a monorepo context

Proposal.

It would be amazing for many people to only subscribe to "Releases only" instead of "Watching" in order to stay updated on the latest news in the template and not receive emails for all individual issues.

It would be enough just to use the tags I think, maybe only consecutive increases in version or date (e.g. 2020.05.01-1).

Can you consider the idea?

@frederikhors why would we tag every master commit? Every master commit isn't a release.

I'm going to suggest that this is an extra maintenance headache that we don't have the bandwidth for, and that if you want to be notified of specific releases, it's worth writing a script to use the github API or similar.

If you think it's critical, we could review a PR to do the work you want to do, but I can't guarantee that it would get accepted.

Expected Behavior

Running npm run dev and npm run start successfully starts the dev server or builds production assets.

Actual Behavior

λ npm run dev

> [email protected] dev C:\Users\Christopher\code\svelte-app
> rollup -c -w

[!] Error: No valid exports main found for 'C:\Users\Christopher\code\svelte-app\node_modules\@rollup\pluginutils'
Error: No valid exports main found for 'C:\Users\Christopher\code\svelte-app\node_modules\@rollup\pluginutils'
    at resolveExportsTarget (internal/modules/cjs/loader.js:618:9)
    at applyExports (internal/modules/cjs/loader.js:499:14)
    at resolveExports (internal/modules/cjs/loader.js:548:12)
    at Function.Module._findPath (internal/modules/cjs/loader.js:650:22)
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:948:27)
    at Function.Module._load (internal/modules/cjs/loader.js:854:27)
    at Module.require (internal/modules/cjs/loader.js:1023:19)
    at require (internal/modules/cjs/helpers.js:72:18)
    at Object.<anonymous> (C:\Users\Christopher\code\svelte-app\node_modules\@rollup\plugin-node-resolve\dist\index.js:15:19)
    at Module._compile (internal/modules/cjs/loader.js:1128:30)

Steps to Reproduce

1. Clone repo
2. Run npm install 3 Run npm run dev or npm run build

Notes

Using node v13.3.0 with npm v6.13.1 on Windows 10. This happens on a fresh install, with no changes to the codebase.

Edit: using the latest node LTS v12.18.0 works as expected.