Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Nov 13 21:31
    webpack-bot unlabeled #9937
  • Nov 13 21:31
    webpack-bot unlabeled #9937
  • Nov 13 21:31
    webpack-bot labeled #9937
  • Nov 13 21:29
    webpack-bot labeled #9968
  • Nov 13 21:29
    webpack-bot unlabeled #9968
  • Nov 13 21:12
    THernandez03 synchronize #9968
  • Nov 13 20:47
    webpack-bot labeled #9968
  • Nov 13 20:32
    webpack-bot labeled #9968
  • Nov 13 20:32
    THernandez03 opened #9968
  • Nov 13 20:23
    webpack-bot labeled #9967
  • Nov 13 20:08
    webpack-bot labeled #9967
  • Nov 13 20:07
    dependabot-preview[bot] labeled #9967
  • Nov 13 20:07

    dependabot-preview[bot] on npm_and_yarn

    chore(deps-dev): bump lint-stag… (compare)

  • Nov 13 20:07
    dependabot-preview[bot] opened #9967
  • Nov 13 16:07
    webpack-bot labeled #9966
  • Nov 13 15:57
    smelukov edited #9966
  • Nov 13 15:55
    smelukov edited #9966
  • Nov 13 15:54
    smelukov edited #9966
  • Nov 13 15:51
    webpack-bot labeled #9966
  • Nov 13 15:51
    webpack-bot labeled #9966
Charles Guo
@CharlesGC
hello
Egor Baranov
@goganchic

Hello!

I'm exploring source codes of webpack and mini-css-extract-plugin and I have a question: why two different structures Dependency and Module were introduced? Why Module structure is not enough? If I'm not mistaken Dependency has only information about what should be built and Module has all algorithms about building, caching and so on. Am I correct? In this case in mini-css-extract-plugin CssDependency looks a bit strange, because it does all receives prepared contents from loader and CssModule only exposes prebuilt sources.

harshit786
@harshit786
Hello we are getting problem while running webpack
The changes in the src folder of main.scss
we are changing but nothing reflects
please help us out
Here at stack also we have added the problem
harshit786
@harshit786
Could you provide the path where the files are running ?
Is there anybody?
harshit786
@harshit786
Please reply anybody I am stucking from three days
harshit786
@harshit786
😞
Rogan Louwrens
@hallucinarium
@harshit786 Have you tried importing into index.js (or whatever your entry point is)?
One of my CSS imports via webpack is into index.js is import "./assets/css/base.css";
Tiago Martinho
@tiagosmartinho

hello,

I am trying to load the fonts through vue.config.js. However I am not getting it.

scss

@include font-face(Lato, '/fonts/lato/latoThin', 100, normal, eot woff2 woff svg ttf);

vue.config.js

     ....
     rules: [{
                test: /\.(woff(2)?|ttf|eot|svg)(\?v=\d+\.\d+\.\d+)?$/,
                use: [{
                    loader: 'file-loader',

                    options: {
                        name: 'lato/[name].[ext]',
                        outputPath: 'fonts/'
                    }
                }]
            },

if I remove the first slash from the source path, fonts/lato/latoThin it loads the fonts, but in compile this error appears

* ./fonts/lato/latoThin.eot? in ./node_modules/css-loader/dist/cjs.js??ref--8-oneOf-3-1!./node_modules/postcss-loader/src??ref--8-oneOf-3-2!./node_modules/sass-loader/dist/cjs.js??ref--8-oneOf-3-3!./node_module s/resolve-url-loader!./src/styles/global.scss

and put the bar back in the font path and it works - /fonts/lato/latoThin

Any solution?

Rogan Louwrens
@hallucinarium
Have you tried using the url-loader?
Alternatively, try './fonts/lato/latoThin'
Tiago Martinho
@tiagosmartinho

Alternatively, try './fonts/lato/latoThin'

already tried this way

Have you tried using the url-loader?

Not yet, I'll try

harshit786
@harshit786

Encore.addStyleEntry('styles.min', './src/css/main.scss');

/**
 * JavaScript Entry Point
 */
Encore.addEntry('main.min', './src/js/main.js');

@ Rogan

these two files
Rogan Louwrens
@hallucinarium
@harshit786 Which framework are you using?
harshit786
@harshit786
This is simple
html files
webpack is running through scripts package.json
Here at stack also we have added the problem
even after deleting main.scss
still it is loading on web browser
Rogan Louwrens
@hallucinarium
Hmm, I haven't used webpack-encore before.
Can you try doing an ES6-style import of your stylesheets in your main JS file?
John Marinelli
@johnmarinelli
@rm-rf-etc i would also consider splitting the rule into 2 separate rules; so test for css and sass files and use different loaders independently, instead of checking for both using a regex and using both loaders
i've seen problems when using multiple loaders on 1 file
harshit786
@harshit786
@hallucinarium could you provide an example
regarding ES6-style import of your stylesheets in your main JS file?
deAtog
@deAtog
@harshit786 Encore.addEntry and Encore.addStyleEntry both do the same thing. To be honest, I'm not sure why Encore separated the two unless it was for historical reasons?
deAtog
@deAtog
@harshit786 I'm confused about the issue you are trying to solve.. how are you running Webpack?
harshit786
@harshit786
I am running pages/home.html directly
is my directory structure
is the pages and I am running directly is it something wrong I am doing as I am novoice to webpack
now in the src folder I do changes in main.scss nothing
happened
harshit786
@harshit786
Here is the main.scss
deAtog
@deAtog
@harshit786 what are you using to serve your files? Webpack's dev server?
harshit786
@harshit786
I am trying to rebuild webpack but it is not working
we are running directly