-
Notifications
You must be signed in to change notification settings - Fork 13
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
webpack #3
Comments
Says who? I will use whatever I want. |
I am totally ok with turning this into an actual site with guidance on more topics above what I talked about for dotnetConf if that's what people want to see :). For bundling and minification I know @madskristensen has some stuff coming that shows a different bundling option. We could perhaps update this to use that now. What do you think Mads? |
I've written a Webpack Task Runner extension that may be helpful. We won't be shipping Gulp as part of our project templates in the next Preview tooling update, so no converting needed |
@madskristensen What is target date for public tooling update? Here is another "starter kit" that uses webpack: |
Not sure it's public yet, but very soon. |
Instead of all that gulp work can this vnext project be migrated to webpack using microsoft recommended setup?
by now everyone should be using:
we need bundles when in #if RELEASE mode and all files when in #if DEBUG mode
The text was updated successfully, but these errors were encountered: