plunk icon indicating copy to clipboard operation
plunk copied to clipboard

http://plnkr.co/edit/undefined?p=preview

Open FrancescoMussi opened this issue 8 years ago • 14 comments

Just discover this package. It is a very much needed one!

But unfortunately it is not working for me. I have followed all the steps but after I run the plunk command I get this:

http://plnkr.co/edit/undefined?p=preview

Do you know why?

FrancescoMussi avatar Feb 23 '17 18:02 FrancescoMussi

Are you on Windows? What did you do?

iliakan avatar Feb 23 '17 19:02 iliakan

I am on Mac. I have done these steps:

  • Install the package globally
  • authorize the package following the instructions
  • run plunk

My node version is: v6.9.5

FrancescoMussi avatar Feb 23 '17 19:02 FrancescoMussi

exact same thing happens for me...

sjsnider avatar Mar 07 '17 00:03 sjsnider

I'd really love to reproduce that issue :/ Tried on a new Mac, it worked.

iliakan avatar Mar 07 '17 08:03 iliakan

I'm on windows and getting the same issue. Followed all steps correctly.

  • Install the package globally
  • authorize the package following the instructions
  • run plunk

My node version is 7.7.2

akshitrewari avatar Mar 13 '17 14:03 akshitrewari

Same issue. Windows 7

Install plunk globally Authorize with .plunk_config.json run plunk get error about missing module "chalk" npm install chalk in plunk directory back to project directory run plunk http://plnkr.co/edit/undefined?p=preview

jacobbutton avatar Apr 06 '17 16:04 jacobbutton

Same issue. Ubuntu

Install plunk globally Authorize with .plunk_config.json run plunk get error about missing module "chalk" npm install chalk globally back to project directory run plunk http://plnkr.co/edit/undefined?p=preview

node -v v7.9.0

[email protected]

Shpiller avatar May 13 '17 04:05 Shpiller

For valid codes there are no issues. The codes which are breaking the cli are the codes which doesn't save successfully on plunker. ie which throws 400 (Bad Request) on pressing the save button at plunkr

screen shot 2017-05-22 at 10 35 09 am

I think we should modify it to throw appropiate error than fail silently.

ishandutta2007 avatar May 22 '17 05:05 ishandutta2007

What you mean? Plunker does not compile the code, it's not a compiler.

How to reproduce the problem?

iliakan avatar May 22 '17 08:05 iliakan

Steps to reproduce the problem:

  • Write any code on plnkr.co which on pressing the save button, throws 400
  • Create a directory locally
  • Copy that same code to that local directory
  • cd to that above created directory
  • Run plunk

ishandutta2007 avatar May 22 '17 10:05 ishandutta2007

How to write such code that gives 400? My code saves successfully. :)

iliakan avatar May 22 '17 10:05 iliakan

sorry I am not able to produce now either, but was surely able to earlier the way I mentioned above, can't recall what exactly I did that time, I am not faking, see I had posted sceenshot earlier too. For now I am able to reproduce another way, for any large repo, I keep deleting files/directories one by one and keep running plank incrementally, it succeeds below a certain limit of folder size(most probably 2MB). So most likely its a scaling issue.

ishandutta2007 avatar May 22 '17 14:05 ishandutta2007

It would be better if you could skip binary files/assets and only whitelist for cetain file extenstions, and after that if the directory is still too big to upload maybe upload partially and notify the user about it.

ishandutta2007 avatar May 22 '17 14:05 ishandutta2007

I had the same problem as described above, when running this tool on windows. Excluding the project's /img folder solved it. Seems like this tool can't handle .jpg or .gif files.

pawod avatar Jun 21 '17 10:06 pawod