autoprefixer-loader | Webpack loader for autoprefixer | Style Language library
kandi X-RAY | autoprefixer-loader Summary
kandi X-RAY | autoprefixer-loader Summary
Webpack loader for autoprefixer
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 autoprefixer-loader
autoprefixer-loader Key Features
autoprefixer-loader Examples and Code Snippets
Community Discussions
Trending Discussions on autoprefixer-loader
QUESTION
I try to import my variables.stylus in my vue component, but when i use @import "~@themes/variables.stylus", webpack throw error: failed to locate @import file ~@themes/variables.stylus.styl
webpack config
...ANSWER
Answered 2019-Apr-04 at 10:25I believe it should be like this:
QUESTION
I've created webpack config to my VueJS project. I want to separate styles from javascript code. I've used mini-css-extract-plugin but finally I receive only bundle.js file. What's wrong with this config and where is a mistake? Is there any missing loader. My config is below:
...ANSWER
Answered 2018-May-21 at 06:17Note that any imported file is subject to tree shaking. This means if you use something like css-loader in your project and import a CSS file, it needs to be added to the side effect list so it will not be unintentionally dropped in production mode. Blockquote
in your package.json, add:
QUESTION
I'm trying to create a super simple webpack set up to create the css from sass
I have the files:
index.html
entry.js
package.json
webpack.config.js
css
-app.scss
index.html:
...ANSWER
Answered 2018-Aug-02 at 16:58module.exports = {
entry: "./entry.js",
output: {
path: __dirname,
filename: "bundle.js"
},
module: {
rules: [
{
test: /\.scss$/,
use: [ 'style-loader','css-loader','postcss-loader' ]
}
]
}
};
QUESTION
I am using Webpack 4 and trying to add support for my css for multiple browsers.
For some reason the way I am doing is not working. Anyone knows how do we fix autoprefixer for webpack 4.
This is my webpack.config
...ANSWER
Answered 2018-May-10 at 00:32According to official documentation 'autoprefixer-loader' is deprecated so that may be the reason it is not working with webpack 4
Use 'postcss-loader' using a config file like
QUESTION
In, my Vue.JS project, after I run :
...ANSWER
Answered 2018-Apr-08 at 16:21Your webpack.output.path configuration is the dist directory.
The HTMLWebpackPlugin.filename is relative to the dist directory. The filename you specified would save your HTML file in the directory above dist.
Try using ./index_prod.html instead, if you want the HTML file to be saved in your dist directory..
QUESTION
This is my webpack.config file. When I run webpack, bundle.js correctly writes to project/dist/assets/bundle.js.
However, when I run npm start to serve up the files, I get an error:
Error: output.path needs to be an absolute path or /.
So... if I make the path absolute: "/dist/assets" or path: __dirname + "/dist/assets" then it serves up the files fine, and emits bundle.js, but it doesn't actually write it to my project/dist/assets folder.
The page looks fine and when I view source, I see but it only exists on the localhost (publicPath).
Where am I going wrong? The goal being for npm start to write the bundle to my project folder AND serve it up with devServer.
...ANSWER
Answered 2017-Mar-03 at 04:46Use path for this:
QUESTION
I'm attempting to use webpack v3 to test long term caching. When I build twice by webpack(just make a change to index.jsx file), and the hash value changed to vendor file.
Reference：Caching
...ANSWER
Answered 2017-Jul-21 at 14:48filename in output use chunkhash, and reset the CommonsChunkPlugin name: ['vendor', 'manifest']
QUESTION
Updated webpack to the latest version(2.6.1), so the webpack config file, that came with the boilerplate, became outdated...
Looked at the official documentation on migration, but still a bit lost regarding how exactly i need to update my config file:
...ANSWER
Answered 2017-Jun-15 at 16:23In the end there were few deletion of the deprecated plugin calls and restructuring some of the fields. Here is the 2.6.1 compatible version, the parts of the file that were changed:
QUESTION
Currently I'm struggling to get HMR working in my Webpack 2 setup. I'll explain my entire setup so I hope this is enough for someone to understand what's happening.
The structure of my project:
...ANSWER
Answered 2017-Apr-19 at 15:56The imports are static and after an update has been identified in module.hot.accept you render the exact same component again, as the TodoApp still holds the old version of your module and HMR realises that and doesn't refresh or change anything in your app.
You want to use Dynamic import: import(). To make it work with babel you need to add babel-plugin-syntax-dynamic-import, otherwise it will report a syntax error as it didn't expect import to be used as a function. The react-hot-loader/babel is not needed if you use react-hot-loader/patch in your webpack config, so your plugins in your .babelrc become:
QUESTION
I am trying to migrate from webpack 1 to 2 based on this guide. I have made most of the changes but struggling with ExtractTextPlugin. This is how it currently looks with webpack 1:
...ANSWER
Answered 2017-Mar-28 at 21:57You're using stylus-loader for your .css as well. But not all CSS is valid stylus. You need to remove stylus-loader from the .css rule:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install autoprefixer-loader
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
