forked from weyj4/sails-webpack
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Issue with bootstrapping #1
Comments
Also, you should put
at the top of |
BaggersIO
added a commit
to BaggersIO/sails-webpack
that referenced
this issue
Jan 4, 2016
Updated docs for an easier implementation.
+1 @tylercollier Yep, I ran into the same issue. Just created a PR. |
Looks great, thanks! On Mon, Jan 4, 2016 at 2:04 PM, Peter Müller [email protected]
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#1. Output path
I'm thinking the example config file is misleading. It says to put it in
config/webpack.js
, but then shows this:Won't that make the output path
config/.tmp/public/js
? It does for me. To fix, I changed the second argument topath.resolve
to be../.tmp/public/js
.#2. Loading webpacked assets
There's no mention of it, but shouldn't we put something like the following in the layout.ejs?
The text was updated successfully, but these errors were encountered: