Skip to content
This repository has been archived by the owner on Aug 3, 2023. It is now read-only.

Enforce one webpack config #245

Merged
merged 1 commit into from
Jun 14, 2019
Merged

Enforce one webpack config #245

merged 1 commit into from
Jun 14, 2019

Conversation

xtuc
Copy link
Member

@xtuc xtuc commented Jun 13, 2019

We don't support multiple webpack configurations, for better UX we
should make sure to enforce it.

The motiviation is that we can't infer which bundle (or configuration)
is meant to be deployed as a worker.

We don't support multiple webpack configurations, for better UX we
should make sure to enforce it.

The motiviation is that we can't infer which bundle (or configuration)
is meant to be deployed as a worker.
@@ -0,0 +1 @@
{}
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be good to auto generate the package.json too, but not very important at the moment

@@ -3,10 +3,16 @@ const { join } = require("path");
const { writeFileSync } = require("fs");
const WasmMainTemplatePlugin = require("webpack/lib/wasm/WasmMainTemplatePlugin");

function error(msg) {
console.error("Error: " + msg);
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made this to avoid showing a stack strace

@xtuc xtuc merged commit 4a4d0f0 into master Jun 14, 2019
@delete-merged-branch delete-merged-branch bot deleted the feat-add-webpack-config-check branch June 14, 2019 09:17
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant