@laheadle its a temlpate 🙂

that fills in :output-to with the :output-in options, and fills in :final-output-to with output-to + “_bundle.js”

Can't seem to figure it out.

oh you are trying to use it?

yes trying to pull in an npm module

@laheadle you skipped the :final-output-to after the “-o”

you can try the command on the command line

doh

trying the command on the command line after your initial compile is a good way to figure out any glitches in your set up

I have to head out but I’ll be available tomorrow if you have more questions

ok. Not sure which command I should try from the command line. I am running from the command line: clj -m figwheel.main --build dev

oh maybe webpack from command line

ok fixed webpack a bit

still getting :bundle-cmd :none failed

Ok found an error with clj -m figwheel.main --build-once dev

my npm dep needed react in package.json. seems to be working now.

I see I don't need to make my own webpack.config.js

Ok I've made a lot of progress. Currently trying to figure out how to get figwheel to tell webpack to export React as a global on window, so rum can refer to it using js/React.

I cannot believe how good the figwheel docs are. Seriously, so good. So complete. A pleasure to read. Almost like they were written by a Fun driven developer or something.

thanks!

Yeah rum needs to change the way it imports react

you can still use cljsjs/react in the meantime to support rum

or you can set! window[“React”] = react

@laheadle ^

https://github.com/tonsky/rum/issues/211

I have yet to update the docs on using npm modules and webpack

Ok I am up and running. Thanks a million @bhauman

cool did you update an older project?

@laheadle ^

Yeah, I had a small one I started a few months ago.

This should improve the workflow

you can now just do npm add lib and use it

absolutely. 3rd party react hooks ecosystem is spread out before us like a buffet.

🙂

also another thing you can do is run webpack on the command line with the -w flag after figwheel has launched

does figwheel create a webpack.config.js?

no

one isn’t needed if you are doing simple things

gotcha

I'm using firebase importing the npm package, this is what I have in index.js

import * as firebase from 'firebase/app';                                          
import "firebase/analytics";                                                       
import 'firebase/auth';                                                            
import 'firebase/database';                                                        
window["firebase"] = firebase;

(ns myapp.firebase                                                                 
  (:require                                                                        
    [firebase]                                                                     
    ))

(def firebase-db                                                                   
  (do                                                                              
    (when (= 0 (some-> firebase .-apps .-length))                                  
      (-> firebase (.initializeApp firebase-config)))                              
    (-> firebase (.database)))) 

@jpsoares106 yeah this is an externs problem

The good news is that this may be fixed with the new npm support in ClojureScript

I’m intending to write a tutorial on how to use these new features on Monday

ha did you just push a change to the 0.2.6 snapshot, bruce? Seemed to fix a console warning about :after-hook not being found :thinking_face: 🎉

I did but I don’t know what would have caused that