Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 02:54
    webpack-bot labeled #14315
  • 02:14
    webpack-bot labeled #14315
  • 02:14
    dependabot[bot] labeled #14315
  • 02:14
    dependabot[bot] opened #14315
  • 02:14

    dependabot[bot] on npm_and_yarn

    chore(deps): bump enhanced-reso… (compare)

  • 02:12

    webpack-bot on main

    chore(deps): bump browserslist … Merge pull request #14308 from … (compare)

  • 02:12

    webpack-bot on npm_and_yarn

    (compare)

  • 02:11
    webpack-bot closed #14308
  • Sep 23 22:17
    webpack-bot labeled #14306
  • Sep 23 22:17
    webpack-bot unlabeled #14306
  • Sep 23 22:06
    sokra edited #14306
  • Sep 23 21:50
    sokra synchronize #14306
  • Sep 23 21:50

    sokra on hashing

    allow to configure all hash fun… allows to select `xxhash64` as … use xxhash64 for future defaults and 1 more (compare)

  • Sep 23 19:01
    gthb edited #14313
  • Sep 23 18:21
    webpack-bot labeled #14313
  • Sep 23 18:21
    webpack-bot labeled #14313
  • Sep 23 18:21
    gthb opened #14313
  • Sep 23 12:31
    webpack-bot labeled #14035
  • Sep 23 12:31
    webpack-bot unlabeled #14035
  • Sep 23 02:25
    webpack-bot labeled #14308
Raghava
@Raghav009
@rm-rf-etc thanks for the inputs
dagtveit
@dagtveit
can somone tell me the difference between the webpack dev server and build command wy dosnt the webpackdev server run the webpackcopy plugin
Raghava
@Raghav009
@dagtveit you can use webpack to watch your files but you need to configure them check this link "https://webpack.js.org/configuration/watch/#watch"
dagtveit
@dagtveit
i have 2 problems i think wanna solve the first one first.
and that is when i run the webpack dev server i am missing my settings.js files which is from a copy command
new CopyWebpackPlugin([
      {from: '**/*.js', to: outDir + '/activesetting', ignore: ['.*'], context: './settings/dev/'},
      {from: './settings', to: outDir + '/settings', ignore: ['.*']}, .......
so first of all it dosnt seem like the dev server is running any of those
dagtveit
@dagtveit
why arent those included in the dev server
Alexander Akait
@alexander-akait
because devserver works in memory
you need look in writeToDisk option
for devserver
dagtveit
@dagtveit
ok i fixed part of it with inlduing the file in the bundle.
settings was the most important part
dagtveit
@dagtveit
next problem is i have multiple entrypoints
Alexander Akait
@alexander-akait
And?
dagtveit
@dagtveit
and when i use the dev server it looks like it also dosnt build all the entrypoints
Alexander Akait
@alexander-akait
it is build all entrypoints
dagtveit
@dagtveit
is there a way to inspect the folder structyre it creates in memory
Alexander Akait
@alexander-akait
debugging?
dagtveit
@dagtveit
or let me refrase its again plugins like this
new HtmlWebpackPlugin({
  template: 'src/index.ejs',
  //excludeChunks: ['settings'],
  chunks: ['IdriftAppLight', 'AureliaApp', 'css'],
  filename: '/v2/index.html',
  metadata: {
    // available in index.ejs //
    title, baseUrl
  }
}),
new HtmlWebpackPlugin({
  template: 'srclegacy/index.ejs',
  filename: 'index.html',
  chunks: ['iDriftVendor', 'IDriftLegacyApp', 'cssLegacy',],
  metadata: {
    // available in index.ejs //
    title, legacyUrl
  }
}),
and it looks like /v2/index file dosnt exist
Alexander Akait
@alexander-akait
I don't know you need read docs for HtmlWebpackPlugin
dagtveit
@dagtveit
all works when i build
but not when i run the dev server again
should this also need to write to disk
how does dev server choose what to build
or what plugins to use
dagtveit
@dagtveit
i see when i go to the /v2 url that it falls back to /dist/index.html
so why dosnt it also run the other plugins
and setting writeToDisk: true confirms this that it dosnt include the v2 file
dagtveit
@dagtveit
dosnt look like dev server respects that htmlwebpackplugin at all
dagtveit
@dagtveit
please help me here. i am so stuck
Alexander Akait
@alexander-akait
please don't spam
webpack-dev-server output all assets what you build
I can't undestand problem
dagtveit
@dagtveit
if i enable writetodisk on webpackdev server and look at that assets in that folder it is not the same content as if i do a normal build. bu ti can see in the log when starting it
Child HtmlWebpackCompiler:
     3 assets
    Entrypoint HtmlWebpackPlugin_0 = __child-HtmlWebpackPlugin_0
    Entrypoint HtmlWebpackPlugin_1 = __child-HtmlWebpackPlugin_1
    Entrypoint HtmlWebpackPlugin_2 = __child-HtmlWebpackPlugin_2
Alexander Akait
@alexander-akait
What is difference, devserver doesn't change in you configuration
dagtveit
@dagtveit
i am missing the /v2/ folder where there should be another index file
Alexander Akait
@alexander-akait
debug code
it is easy
dagtveit
@dagtveit
i have no ide how to do that on webpack. but i found something in the log here can this be a problem. do i have to manualy map out the dirrent folders
 [6] multi (webpack)-dev-server/client?http://localhost aurelia-webpack-plugin/runtime/empty-entry aurelia-webpack-plugin/runtime/pal-loader-entry aurelia-bootstrapper 64 bytes {AureliaApp~d0ae3f07} [built]
 [9] multi (webpack)-dev-server/client?http://localhost ./settings/Active/Settings.js 40 bytes {Settings~d0ae3f07} [built]
nvm i was just confused by the formatting i think. so how would you go about debugging this
dagtveit
@dagtveit
is there a way ti make the dev server only server the files already there ? then i can just start build first. then start the server
seems like upgrading some packages fixed it :)
Alex Barker
@kwhat
Is there a way to debug what is going on with webpack? I have a file I am packing that does some include/require for jquery and datatables, and that works... as long as jquery and datatables are in the same file. If I move datatables to its own JS file, everything breaks as now datatables seems to have disappeared despite being in the new file and being loaded. Is there a way to figure out what is going so sideways? http://dpaste.com/0233DYJ
Alex Barker
@kwhat
sigh, what a dumpster fire.
Alex Barker
@kwhat
Another 4 hours wasted on webpack... what an unbelievable fucking heap of shit.
Alexander Akait
@alexander-akait
Are you sure it is problem in webpack?
Maybe better read how JavaScript work before shitting everything