plunk
plunk copied to clipboard
http://plnkr.co/edit/undefined?p=preview
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?
Are you on Windows? What did you do?
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
exact same thing happens for me...
I'd really love to reproduce that issue :/ Tried on a new Mac, it worked.
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
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
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
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
I think we should modify it to throw appropiate error than fail silently.
What you mean? Plunker does not compile the code, it's not a compiler.
How to reproduce the problem?
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
How to write such code that gives 400? My code saves successfully. :)
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.
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.
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.