Question: has anyone here written a webpack plugin? struggling with a few concepts

Asked By
Asked At
2018-01-10 15:20:03

Found 15 possible answers.

User Answered At Possible Answer
eeue56 2018-01-10 15:38:01 Yes :grinning: @ingara when was your talk btw?
ingara 2018-01-10 15:46:55 It's on friday at CodeMash. @erikwendel is doing one there on Thursday too
eeue56 2018-01-10 15:47:32 chokidar -c 'elm-make --docs' src/ is probably a pretty good replacement for now :grinning: I don't think we'll get a PR through by then
ingara 2018-01-10 16:08:06 It's no rush. I'm using elm-live and that's working fine for now :-)
eeue56 2018-01-16 10:00:50 @razzeee what path are you giving to the elm-make?
razzeee 2018-01-16 10:04:37 well I tried a bunch so far :smile: @razzeee uploaded a file: image.png and should work :disappointed: which translates to /home/travis/.nvm/versions/node/v8.9.1/bin/elm-make at the moment this:
eeue56 2018-01-16 10:21:02 that path looks wrong look at the path in the error message when it tried to find the compiler :slightly_smiling_face: you've got a " in there you shouldn't have
razzeee 2018-01-16 10:21:57 yeah, lets see if that was c&p or is really in my script
eeue56 2018-01-16 10:22:08 it is really in the script
razzeee 2018-01-16 10:22:08 I'm trying to debug it in a vm atm
eeue56 2018-01-16 10:22:24 you have this use: ['elm-hot-loader', 'elm-webpack-loader?verbose=true&warn=true&pathToMake="'+ prefix + '/bin/elm-make'], after path to make the difference is no " it should be use: ['elm-hot-loader', 'elm-webpack-loader?verbose=true&warn=true&pathToMake='+ prefix + '/bin/elm-make'], probably
razzeee 2018-01-16 10:24:40 crap, how did that happen :smile: thank you :raised_hands: it worked finally
ivanbanov 2018-02-06 13:45:25 Would it be possible to have colourful errors in the console? about the errors, :neutral_face:
gorghoa 2018-02-22 16:26:00 Hello :slightly_smiling_face: thanks for any hint! (note that I was intially wanted webpack instead of elm-make because I have some js/ts files I would like to build in the same time) but when I load my bundle, it results with Elm is undefined (how ironic)
    path: path.resolve(__dirname, 'web/js')
    filename: '[name].bundle.js',
  output: {
      'vue$': 'vue/dist/vue.common.js'
    alias: {
    extensions: [ ".tsx", ".ts", ".js" ],
  resolve: {
    noParse: /\.elm$/
        loader:  'elm-webpack-loader?verbose=true&warn=true',
        exclude: [/elm-stuff/, /node_modules/],
        test:    /\.elm$/,
        exclude: /node_modules/
        use: 'ts-loader',
        test: /\.tsx?$/,
    rules: [
  module: {
  devtool: "inline-source-map",
    'erdv-consult': './src/Nnx/FluxFtthBundle/Resources/views/eRDV/ERDVConsult.elm',
    'import-file': './src/Nnx/FluxFtthBundle/Resources/private/typescript/import-fichier-flux.ts',
  entry: {
module.exports = {
For now, my webpcak config :
const path = require('path'); Quick question, i’m building some elm with webpack, I would like webpack to output a “standalone” bundle so I can directly load my script via

Related Questions