Skip to content
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

Version 2.1.0 gives error "file" argument must be a non-empty string #310

Closed
dhimmel opened this issue Aug 1, 2019 · 9 comments
Closed

Comments

@dhimmel
Copy link

dhimmel commented Aug 1, 2019

Version 2.1.0 produces the following error (CI logs):

"file" argument must be a non-empty string 

Downgrading to version 2.0.1 fixed the issue.

Our gh-pages command was:

gh-pages \
  --dist build \
  --branch build \
  --user 'CircleCI Deploy Job <[email protected]>' \
  --message 'Deploy npm package on 2019-08-01
Builds https://github.com/hetio/frontend-components/commit/bf3e385fd25f8884e6301321642474b084143c40
Pushed by https://circleci.com/gh/hetio/frontend-components/33
[skip ci]'

The error occurred before a build branch existed and after we initialized an empty orphan build branch in hetio/frontend-components@b65b408.

Possibly related to #308. CC @vincerubinetti.

dhimmel referenced this issue in hetio/frontend-components Aug 1, 2019
"file" argument must be a non-empty string
Exited with code 1
https://circleci.com/gh/hetio/frontend-components/17
ahuth added a commit to ahuth/frostbite that referenced this issue Aug 2, 2019
@doogthemushroom
Copy link

Also experiencing this issue with 2.1. Reverting back to 2.0.1 resolves the issue.

schorfES pushed a commit to nrmnrsh/nrmnrsh.com that referenced this issue Aug 4, 2019
tdooner added a commit to tdooner/brigade-jekyll that referenced this issue Aug 5, 2019
@sassouiabd
Copy link

sassouiabd commented Aug 6, 2019

I have also experienced this issue: "npm deploy is failing with "file" argument must be a non-empty string.
I thought the problem was coming from npm... until i saw this thread.

@shpiglify
Copy link

thats a huge issue !

@vakeeel
Copy link

vakeeel commented Aug 7, 2019

When can we expect this to be fixed and released?

@azangru
Copy link

azangru commented Aug 12, 2019

Doesn’t release 2.1.1 close this issue?

@nytamin
Copy link

nytamin commented Aug 19, 2019

Yes, can confirm that upgrading to 2.1.1 fixes this

@dhimmel
Copy link
Author

dhimmel commented Aug 20, 2019

Here are the changes from 2.1.0 to 2.1.1. Would be nice to know what change fixed this issue before closing it. @tschaub mind letting us know and confirming this is fixed?

@azangru
Copy link

azangru commented Aug 20, 2019

@dhimmel I am sure it was this PR: #312

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants