-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Flow.js causes build error (Warning: Unable to read "dist/public/bower_components/flow.js" file (Error code: EISDIR)) #1064
Comments
@jshultz which task is failing? Small log post please? |
Sure, here you go: Running "usemin:js" (usemin) task Processing as JS - dist/public/app/8d8978e0.vendor.js Processing as JS - dist/public/app/e60d0032.app.js Processing as JS - dist/public/bower_components/flow.js |
@jshultz can you try something for me? rev: {
dist: {
files: {
src: [
'<%= yeoman.dist %>/client/{,*/}*.js',
'<%= yeoman.dist %>/client/{,*/}*.css',
'<%= yeoman.dist %>/client/assets/images/{,*/}*.{png,jpg,jpeg,gif,webp,svg}',
'<%= yeoman.dist %>/client/assets/fonts/*'
]
}
}
}, to this: rev: {
dist: {
files: {
src: [
'<%= yeoman.dist %>/client/!(bower_components)/{,*/}*.js',
'<%= yeoman.dist %>/client/!(bower_components)/{,*/}*.css',
'<%= yeoman.dist %>/client/assets/images/{,*/}*.{png,jpg,jpeg,gif,webp,svg}',
'<%= yeoman.dist %>/client/assets/fonts/*'
]
}
}
}, |
Mine doesn't look like that? Mine looks like:
|
Sorry, that was my mistake (copying from the wrong branch). How about changing it to this: rev: {
dist: {
files: {
src: [
'<%= yeoman.dist %>/public/!(bower_components)/{,*/}*.js',
'<%= yeoman.dist %>/public/!(bower_components)/{,*/}*.css',
'<%= yeoman.dist %>/public/assets/images/{,*/}*.{png,jpg,jpeg,gif,webp,svg}',
'<%= yeoman.dist %>/public/assets/fonts/*'
]
}
}
}, (same concept just replace |
No worries, I've been there before. So, I tried that and:
resulting in:
|
Well, that seemed to fix the issue on code generated by the |
can I update an existing application that's already built to the latest version? I'm not sure how that works. I'll let you figure out the first issue first, though. :) |
As far as that goes, there isn't a clear upgrade path for migrating an existing app. |
ok, no biggie I can make that work pretty easy. :) |
Ok, well #1064 (comment) got us a little bit closer. That excluded Now we just need to do the same for the usemin: {
html: ['<%= yeoman.dist %>/public/!(bower_components)/{,*/}*.html'],
css: ['<%= yeoman.dist %>/public/!(bower_components)/{,*/}*.css'],
js: ['<%= yeoman.dist %>/public/!(bower_components)/{,*/}*.js'],
...
}, I think its safe to say that we don't need usemin rewriting asset references in our bower dependencies (: |
Guess what? That fixed all the things! :) Awesome! :) |
@jshultz I'd like to share an interesting tidbit with you. There is a newer version of The other thing is that there is a newer (more maintained) module called |
ok, cool. thanks for the heads up. :) |
Also useful: this is an issue with an folder which has .js in the file name. Examples include, Chart.js, flow.js, etc. Solution from sebdeckers/grunt-rev#29 (comment):
|
Is there a process for resolving or getting around this issue:
Warning: Unable to read "dist/public/bower_components/flow.js" file (Error code: EISDIR)
The only one I've found that works is is a workaround. But I still have to use --force in order to get it to build and deploy correctly.
EDIT: the other problem is, even with this fix, you have to run
grunt build --force
in order for it to work. :/The text was updated successfully, but these errors were encountered: