mquandalle/meteor-bower

Unknown error with empty dependency list

Opened this issue · 7 comments

Scalahansolo commented

When adding this package to my app, everything works fine. However, when I add my first dependency, I get the following error.

While building the application:
   fs.js:488:19: EISDIR, illegal operation on a directory (compiling bower.json)
   at Object.fs.readSync (fs.js:488:19)
   at Object.fs.readSync (/Users/scallahan/.meteor/packages/mquandalle_bower/.1.4.1_1.1yhsji5++os+web.browser+web.cordova/plugin.bower.os/npm/bower/node_modules/bower/node_modules/bower-config/node_modules/graceful-fs/polyfills.js:218:23)
   at Object.fs.readSync (/Users/scallahan/.meteor/packages/mquandalle_bower/.1.4.1_1.1yhsji5++os+web.browser+web.cordova/plugin.bower.os/npm/bower/node_modules/bower/node_modules/bower-registry-client/node_modules/graceful-fs/polyfills.js:218:23)
   at Object.fs.readSync (/Users/scallahan/.meteor/packages/mquandalle_bower/.1.4.1_1.1yhsji5++os+web.browser+web.cordova/plugin.bower.os/npm/bower/node_modules/bower/node_modules/bower-json/node_modules/graceful-fs/polyfills.js:218:23)
   at Object.fs.readFileSync (fs.js:322:28)
   at packages/bower/plugin/handler.js:125:1
   at Array.forEach (native)
   at Function._.each._.forEach (packages/underscore/underscore.js:105:1)
   at packages/bower/plugin/handler.js:122:1
   at Array.forEach (native)
   at Function._.each._.forEach (packages/underscore/underscore.js:105:1)
   at bowerHandler (packages/bower/plugin/handler.js:82:1)
   at Package (packages/bower/plugin/handler.js:248:1)
lorensr commented

Hi! What's the location and contents of your bower.json?

Scalahansolo commented

I have tried in two separate locations. At the top level of my app. As well as at lib/bower/bower.json

Scalahansolo commented

Another thing that is probably worth mentioning. When I have an empty bower file in a completely fresh project, meteor starts up just fine. Once I add my package, I get the following error, but then when I remove that package from the deps list, the error persists.

lorensr commented

Thanks, and contents of the file?

Scalahansolo commented

My bower file looks like this. Unfortunately, I cant share the actual package as it is proprietary. The package however, is just a set of UI styles along with some JS to accompany those.

{
  "name": "meteorfeather",
  "version": "0.0.1",
  "dependencies": {
    "my package": "url for package"
  },
  "ignoredDependencies": [
    "jquery"
  ],
  "private": true
}
lorensr commented

Does it work if you add a public bower package, eg backbone: 1.1.0? What is
the format of your url?

On Tuesday, July 21, 2015, Sean Callahan notifications@github.com wrote:

My bower file looks like this. Unfortunately, I cant share the actual
package as it is proprietary.

{
"name": "meteorfeather",
"version": "0.0.1",
"dependencies": {
"my package": "url for package"
},
"ignoredDependencies": [
"jquery"
],
"private": true
}

—
Reply to this email directly or view it on GitHub
#92 (comment)
.

Scalahansolo commented

It works with react-bootstrap and react just. I am combing through the packages that are brought in through my deps chain, and the one major difference I have spotted so far is that they all contain a package.json file, and in many of those files there is a scripts field.

I am also trying to track down what JS files are getting brought in that are breaking things.

EDIT: In a bunch of the brought in packages through the deps chains, there is a dist folder. I continue to get errors until this file is deleted. Once that is gone, meteor starts.