-
Notifications
You must be signed in to change notification settings - Fork 486
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not compatible with webpack2 #349
Comments
Can confirm. Having the same problem when upgrading to webpack 2.2.1 |
Webpack 1 used the |
this worked for me on Webpack2 |
This works. But when I try to server render I get a |
Same Issue for me. When using
Getting error init is not a function if use
Server side rendering is not working. Getting error document is not defined |
@javidan did you test my suggestion? |
@javidan do you know the reason importing from 'director/build/director' works? |
@ClearedFram3 see my comment above. Webpack 1 used to read the |
Correct import introduction
|
When I upgraded to webpack2/npm(4.1.2), it raised the following runtime error:
Uncaught TypeError: this.configure is not a function at Object.exports.Router (webpack:///./~/director/lib/director/router.js?:181) at init (webpack:///./app/view/router.jsx?:58) at eval (webpack:///./app/view/router.jsx?:121) at Object.212 (app.js:2) at n (vendor.js:1) at eval (webpack:///./app/main.js?:5) at Object.529 (app.js:9) at n (vendor.js:1) at window.webpackJsonp (vendor.js:1) at app.js:1
I figured it out that webpack2 somehow did not recognize the ./build path, instead it used ./lib path, which is declared in package.json("main": "./lib/director"). I believe there are some issues because what's in the ./lib is not complete code and we can only use the code in ./build path.
However, I am wondering why it worked fined with webpack1. Plese let me know what happened here. thanks :)
The text was updated successfully, but these errors were encountered: