-
Notifications
You must be signed in to change notification settings - Fork 59
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.
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
Embedded #31
base: embedded
Are you sure you want to change the base?
Embedded #31
Conversation
@@ -6,13 +6,13 @@ const APP_DIR = path.resolve(__dirname, "source/"); | |||
const config = | |||
{ | |||
mode: "development", | |||
target: "web", | |||
target: "node", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we should make two different webpack config files. One for webpacking for node and one for web. Maybe webpack.node.config.js and webpack.web.config.js and then have two separate scripts in package.json for building each. Probably want to configure each to build a different .min.js file for each too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's probably a good idea
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although I wonder how other libraries handle this such that you can reference a single npm module for both. I think for now two versions of webpack.config is probably most efficient, but I would like to see if there's something inherently more efficient for this...
Added support for node