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.

Sign up for GitHub

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

Jump to bottom

Start dotnet compiler in package.json instead of snowpack.config.js #53

Open

MichaelMay81 opened this issue Feb 1, 2022 · 1 comment

MichaelMay81 commented Feb 1, 2022

Snowpacks plugin-run-script seems buggy:

Not running script before build (e.g., [BUG] plugin-run-script not waiting for eleventy to finish during build FredKSchott/snowpack#3095)
Not killing child processes (e.g., Windows: execa leaving processes around when running npm scripts in a sh shell sindresorhus/execa#433)

Proposed solution:
Instead of starting dotnet fable inside snowpack.config.js, start int in package.json

"scripts": {
    "postinstall": "dotnet tool restore",
    "dev": "dotnet fable watch src -o dist --run snowpack dev",
    "prebuild": "dotnet fable src -o dist",
    "build": "snowpack build",
    "clean": "rm -r dist build"
  },

The text was updated successfully, but these errors were encountered:

Author

MichaelMay81 commented Feb 1, 2022

'devOptions: { output: "stream" }'
gives better output with dotnet not being started by snowpack

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment