Can I add a Vue single file component to an existing application without using WebPack?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I would like to introduce Vue to an existing ASP.NET MVC app. If we intend to use Vue’s single file components, will we need to add WebPack to the build process?
Currently, our application uses ASP.NET bundles but does no additional compiling/processing of Javascript or CSS. I am trying to understand how adding Vue (or any front-end Javascript framework) will impact the build process.
asp.net-mvc vue.js webpack
add a comment |
I would like to introduce Vue to an existing ASP.NET MVC app. If we intend to use Vue’s single file components, will we need to add WebPack to the build process?
Currently, our application uses ASP.NET bundles but does no additional compiling/processing of Javascript or CSS. I am trying to understand how adding Vue (or any front-end Javascript framework) will impact the build process.
asp.net-mvc vue.js webpack
add a comment |
I would like to introduce Vue to an existing ASP.NET MVC app. If we intend to use Vue’s single file components, will we need to add WebPack to the build process?
Currently, our application uses ASP.NET bundles but does no additional compiling/processing of Javascript or CSS. I am trying to understand how adding Vue (or any front-end Javascript framework) will impact the build process.
asp.net-mvc vue.js webpack
I would like to introduce Vue to an existing ASP.NET MVC app. If we intend to use Vue’s single file components, will we need to add WebPack to the build process?
Currently, our application uses ASP.NET bundles but does no additional compiling/processing of Javascript or CSS. I am trying to understand how adding Vue (or any front-end Javascript framework) will impact the build process.
asp.net-mvc vue.js webpack
asp.net-mvc vue.js webpack
asked Nov 21 '18 at 20:51
flipdoubtflipdoubt
6,865125387
6,865125387
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
If you want to use Single File Components then you would need a build tool like Webpack. Check out the deployment guide for more info on that.
If you want to include it with a script tag and use normal HTML and JS(without build tools - also the deployment guide) then that should work without changing the build process. I haven't tested it with Razor templates(.cshtml
), and the v-on
shorthand might cause some issues there.
I'm looking to do the exact same thing right now, and I'm thinking the best way to get started is with the script tag, but I'm a big fan of the single file components
Edit: Just confirmed that everything is pretty good in Razor templates except the v-on
shorthand, so if you avoid that it should be fine.
The following worked in a .cshtml
file:
<!-- Don't do `@click`! Use `v-on:click` instead -->
<div id="vueApp" v-on:click="alert(message)">
{{ message }}
<ul>
<li :title="item" v-for="item in itemList">{{ item }}</li>
</ul>
</div>
<script src="https://cdn.jsdelivr.net/npm/vue/dist/vue.js"></script>
<script>
let vueApp = new Vue({
el: '#vueApp',
data: {
message: 'Hello!',
itemList: ['1', '2', '3']
},
methods: {
alert (msg) {
// got an error using `alert` in the template, but this was fine
window.alert(msg)
}
}
})
</script>
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53420284%2fcan-i-add-a-vue-single-file-component-to-an-existing-application-without-using-w%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you want to use Single File Components then you would need a build tool like Webpack. Check out the deployment guide for more info on that.
If you want to include it with a script tag and use normal HTML and JS(without build tools - also the deployment guide) then that should work without changing the build process. I haven't tested it with Razor templates(.cshtml
), and the v-on
shorthand might cause some issues there.
I'm looking to do the exact same thing right now, and I'm thinking the best way to get started is with the script tag, but I'm a big fan of the single file components
Edit: Just confirmed that everything is pretty good in Razor templates except the v-on
shorthand, so if you avoid that it should be fine.
The following worked in a .cshtml
file:
<!-- Don't do `@click`! Use `v-on:click` instead -->
<div id="vueApp" v-on:click="alert(message)">
{{ message }}
<ul>
<li :title="item" v-for="item in itemList">{{ item }}</li>
</ul>
</div>
<script src="https://cdn.jsdelivr.net/npm/vue/dist/vue.js"></script>
<script>
let vueApp = new Vue({
el: '#vueApp',
data: {
message: 'Hello!',
itemList: ['1', '2', '3']
},
methods: {
alert (msg) {
// got an error using `alert` in the template, but this was fine
window.alert(msg)
}
}
})
</script>
add a comment |
If you want to use Single File Components then you would need a build tool like Webpack. Check out the deployment guide for more info on that.
If you want to include it with a script tag and use normal HTML and JS(without build tools - also the deployment guide) then that should work without changing the build process. I haven't tested it with Razor templates(.cshtml
), and the v-on
shorthand might cause some issues there.
I'm looking to do the exact same thing right now, and I'm thinking the best way to get started is with the script tag, but I'm a big fan of the single file components
Edit: Just confirmed that everything is pretty good in Razor templates except the v-on
shorthand, so if you avoid that it should be fine.
The following worked in a .cshtml
file:
<!-- Don't do `@click`! Use `v-on:click` instead -->
<div id="vueApp" v-on:click="alert(message)">
{{ message }}
<ul>
<li :title="item" v-for="item in itemList">{{ item }}</li>
</ul>
</div>
<script src="https://cdn.jsdelivr.net/npm/vue/dist/vue.js"></script>
<script>
let vueApp = new Vue({
el: '#vueApp',
data: {
message: 'Hello!',
itemList: ['1', '2', '3']
},
methods: {
alert (msg) {
// got an error using `alert` in the template, but this was fine
window.alert(msg)
}
}
})
</script>
add a comment |
If you want to use Single File Components then you would need a build tool like Webpack. Check out the deployment guide for more info on that.
If you want to include it with a script tag and use normal HTML and JS(without build tools - also the deployment guide) then that should work without changing the build process. I haven't tested it with Razor templates(.cshtml
), and the v-on
shorthand might cause some issues there.
I'm looking to do the exact same thing right now, and I'm thinking the best way to get started is with the script tag, but I'm a big fan of the single file components
Edit: Just confirmed that everything is pretty good in Razor templates except the v-on
shorthand, so if you avoid that it should be fine.
The following worked in a .cshtml
file:
<!-- Don't do `@click`! Use `v-on:click` instead -->
<div id="vueApp" v-on:click="alert(message)">
{{ message }}
<ul>
<li :title="item" v-for="item in itemList">{{ item }}</li>
</ul>
</div>
<script src="https://cdn.jsdelivr.net/npm/vue/dist/vue.js"></script>
<script>
let vueApp = new Vue({
el: '#vueApp',
data: {
message: 'Hello!',
itemList: ['1', '2', '3']
},
methods: {
alert (msg) {
// got an error using `alert` in the template, but this was fine
window.alert(msg)
}
}
})
</script>
If you want to use Single File Components then you would need a build tool like Webpack. Check out the deployment guide for more info on that.
If you want to include it with a script tag and use normal HTML and JS(without build tools - also the deployment guide) then that should work without changing the build process. I haven't tested it with Razor templates(.cshtml
), and the v-on
shorthand might cause some issues there.
I'm looking to do the exact same thing right now, and I'm thinking the best way to get started is with the script tag, but I'm a big fan of the single file components
Edit: Just confirmed that everything is pretty good in Razor templates except the v-on
shorthand, so if you avoid that it should be fine.
The following worked in a .cshtml
file:
<!-- Don't do `@click`! Use `v-on:click` instead -->
<div id="vueApp" v-on:click="alert(message)">
{{ message }}
<ul>
<li :title="item" v-for="item in itemList">{{ item }}</li>
</ul>
</div>
<script src="https://cdn.jsdelivr.net/npm/vue/dist/vue.js"></script>
<script>
let vueApp = new Vue({
el: '#vueApp',
data: {
message: 'Hello!',
itemList: ['1', '2', '3']
},
methods: {
alert (msg) {
// got an error using `alert` in the template, but this was fine
window.alert(msg)
}
}
})
</script>
edited Dec 4 '18 at 13:19
answered Dec 4 '18 at 13:01
Josh GJosh G
132311
132311
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53420284%2fcan-i-add-a-vue-single-file-component-to-an-existing-application-without-using-w%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown