vue-webpack | vue and webpack configration with ES6 postcss eslint | Code Analyzer library
kandi X-RAY | vue-webpack Summary
kandi X-RAY | vue-webpack Summary
vue and webpack configration with ES6 postcss eslint
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of vue-webpack
vue-webpack Key Features
vue-webpack Examples and Code Snippets
Community Discussions
Trending Discussions on vue-webpack
QUESTION
TL;DR
(vue files) + background.ts => ...[webpack]... => (bundled vue files) + background.js
can't execute background.js
expected background.js to contain only "console.log('test');"
I have a vue project with webpack and typescript.
I want my build step to produce a "background.js" file aside from the [vue JS related files].
I have a source file in typescript: "background.ts".
Through the vue.config.js I added a webpack entry "background".
It does build a file "background.js" as I expected
but it is bundled(I think) and it can't be executed by a chrome plugin.
For now all I want is to have a "background.js" file which execute the "console.log('test');" instruction it contains when the script is called.
Thank you, webpack is hell
edit: adding files:
...ANSWER
Answered 2020-Apr-13 at 20:45In short – you don't need a bundler for transpiling a single typescript file. Just use tsc
.
Specifically to this question where the Vue app is used as part of chrome extension, it may make sense to separate building an app and the extension related files.
Another possible option is to use something like Vue CLI Browser Extension Plugin.
QUESTION
I wanna have code coverage on frontend with cypress. Currently cypress recommends istanbul for coverage. Unfortunately I can't use it in pair of the stack below:
- vue-property-decorator
- cypress
- istanbul code coverage.
- typescript.
Because of: - I didn't find a way to make istanbul work with ts-loader, because istanbul-intementer-loader uses babel under the hood - babel-loader doesn't support decorators in the same way that typescript does, that breaks vue-property-decorator. Using vue in typescript w/o vue-property-decorator is not that neat...
Here're some useful link:
- example for repo with babel coverage
- official guide
- official github repo for typescript users
- cypress issue
Here's the repo and quick overview:
git clone https://github.com/akoidan/vue-webpack-typescript && cd vue-webpack-typescript
yarn install
yarn run build
yarn run e2e
You can also check out the babel branch on the repo above, to see example with babel instead of ts-loader
Here's the example of setup with ts-loader:
package.json:
...ANSWER
Answered 2019-Nov-16 at 19:18- there's seem to be no way to make coverage work with ts-loader
- babel 7 + babel-preset-typescript-vue are required to make it work with vue-property-decorator
Here's the example of github repo with working codecov
QUESTION
I'm trying to create a simple web app with material-components-vue and vue-cli with webpack, however, I found out that I cannot import stylesheets from node_modules
without a preceding ~
.
I have tried several webpack/vue-cli configs, and ended up with a config in vue.config.js
passing loader options.
My vue.config.js
looks like this:
ANSWER
Answered 2019-May-03 at 12:13In this configuration your vue.config.js
is ignored. This file is used by @vue/cli-service
, but you're using webpack-dev-server
instead. Thus, your sass-loader
doesn't receive this includePaths
option.
You can either use modern vue create
command, or if you want to modify existing project:
Open
build/utils.js
file.Find
return ...
inexports.cssLoaders
function:
QUESTION
I've been stuck on this problem for days. I've tried everything I can find but still can't get it worked.
In app.js
When I set like below, it works:
ANSWER
Answered 2018-Dec-13 at 09:15There's an error in export default {...}
, the fixed version:
QUESTION
I use the dynamic source for vue-webpack images in nuxt :src="require('path/to/image' + dynamic.variable)" in my project navbar. If the users substitute their image through a form which refetches their information and deletes their previous image I get a webpack error module (img) not found (it does not find the new one): is there a way to solve this, like wait for webpack HRM to finish?
I tried setting up a setTimeout() of one second before user re-fetch and it works, but I don't like a random waiting, I'd use a promise or a sync dynamic, the point is webpack hot reload is not controlled by my functions.. I also tried with setting the dynamic path as a computed: but it doesn't fix.
My image tag:
...ANSWER
Answered 2019-Apr-18 at 22:37First of all, as somebody told you in the comments, webpack hmr shouldn't be used for production.
In Nuxt, everything that you reference from the assets folder will be optimized and bundled into the project package. So the ideal use case for this folder is all assets that can be packaged and optimized, and most likely won't change like fonts, css, background images, icons, etc.
Then, require is called only once by webpack when it is either building the site for local development or building the site for generating a production package. The problem in your case is that you delete the original file while you're in development and webpack tries to read it and fails.
In the case of these images that the user uploads, I think you should use the static folder instead and instead of using require you'll have to change the :src with
QUESTION
I am working on webpack 4.29.3 and vue.js 2.6.3. I just tried to create a simple hello world project with vue js and webpack. I expected index.html
to be rendered well. I get the error, though: SyntaxError: invalid range in character class which is really weird because I don't do anything with regular expression. that's why I am not sure which part to fix it.
vue-first.js:
...ANSWER
Answered 2019-Feb-08 at 09:00QUESTION
I'm trying to follow https://alligator.io/vuejs/demistifying-vue-webpack/ . Based on this I tried:
...ANSWER
Answered 2019-Jan-04 at 17:25You're trying to use a vue-cli 2 command with a vue-cli 3 version.
Since version 3, the command to initialize a new project has changed so to do what you want you're not going to write vue init webpack-simple project
but instead vue create project
QUESTION
I have the following code:
src/store/modules/outcome-analyzer/outcome-analyzer.js
...ANSWER
Answered 2018-Jul-13 at 23:10You misplaced your worker.terminate();
, which you probably wanted in your onmessage
handler. As it is now, the worker is being spawned, but killed almost immediately after.
QUESTION
I never really thought about it until I switched from webpack to brunch where I saw the following lines in index.html:
...ANSWER
Answered 2018-Jul-08 at 08:12The require
keyword is giving errors because it's a made up way to require external files. If you used import
, the standard native implementation, it would work out of the box on newer browsers. Bundlers aren't required.
Require came from https://requirejs.org/
They're looking for that word require
and, essentially, injecting code at that source path into a built file. It'd be like if I made a injectFile
keyword for my InjectFileJS
project.
QUESTION
I'm trying to convert our entire build from requirejs and a mess to webpack, so I'll do my best to keep only the relevant details below.
The error, output in console from webpack
ANSWER
Answered 2018-Feb-23 at 06:14template
refers to a template html file which you offer to the plugin instead of the output path. The plugin will then inject bundle script information to the bottom of the template
.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install vue-webpack
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page