Skip to content
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

Open
leblancmeneses opened this issue Jun 9, 2016 · 5 comments
Open

webpack #3

leblancmeneses opened this issue Jun 9, 2016 · 5 comments

Comments

@leblancmeneses
Copy link

Instead of all that gulp work can this vnext project be migrated to webpack using microsoft recommended setup?

by now everyone should be using:

  1. sass
  2. typescript
  3. bundling, minification for css and js

we need bundles when in #if RELEASE mode and all files when in #if DEBUG mode

@stanislavromanov
Copy link

by now everyone should be using

Says who? I will use whatever I want.

@glennc
Copy link
Owner

glennc commented Jun 10, 2016

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?

@madskristensen
Copy link

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

@leblancmeneses
Copy link
Author

@madskristensen What is target date for public tooling update?

Here is another "starter kit" that uses webpack:
https://github.com/kriasoft/aspnet-starter-kit/blob/master/tools/webpack.config.js

@madskristensen
Copy link

Not sure it's public yet, but very soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants