You can disable SmartScreen in the Windows Defender Security Center app in total or just for Edge, but for the latter it's faster to do so right within Edge itself, particularly if you are already using Edge. Here's how to toggle SmartScreen off and on in Edge:. With SmartScreen off, you are on your own about which files to download in Edge, but I would urge you to go back and toggle SmartScreen on when you have finished downloading your file.
And, of course, only turn it off to download files you know to be safe. Which looks like. This way you can pass the request to be done by your browser so that then the response will be also handled by the browser. This is the crucial difference between doing the request yourself or by the browser. If you do the request yourself then the browser won't download the object but you will receive it yourself to do something with it.
If you wish the browser to download the object, then, make the browser do the request for the object as well! Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Force browser download a large file Ask Question. Asked 5 years, 7 months ago. Active 5 years, 7 months ago.
Viewed 2k times. I'm happy to send a PR but then I will need to re-organize the code into smaller modules, replace all modules that are either redundant or too big in size, and finally make azure-storage-node behave consistently regardless the environment under which it runs. If that's ok for you and you're willing to merge such changes then I'll schedule a day mid-next week to work on this and submit a PR. I can drop browserify-fs because it's useless for the latest publishes. For request module, I have realized most of it's functionalities our library depends, based on native http module.
But the proxy of request module has not been implemented. About splitting into five smaller modules, it has been considered by our architectures as a long term planned item.
In the short term, I'm afraid that we cannot accept breaking changes like that. However, ideas or suggestions are really welcome. I can propose them to our team's discussion and planning. Currently, non-breaking PRs can be accepted, such as removing or replacing redundant modules or codes. For complex changes, better to sync up the design before coding, in case of unexpected conflicting.
XiaoningLiu Imho, generally speaking, the problem goes beyond browserify-fs because when bundled for server-side use aka something like browserify --node.
For example you can see that blobservice. So there must be something fundamentally wrong in the way different modules are being included or loaded it looks like as if different pieces of code and modules are being replicated rather than required. Then you have async that is These are just basic observations I'm sure you'll get a better insight when you look at the module breakdown and find other redundant modules for example underscore , request etc.
I completely understand you don't wish for any breaking changes, but if you guys take a look at the interactive chart and spend little of your time in understanding what's going on, you'd be able to dramatically reduce the size of the module with zero breaking changes and minimal effort on your side.
XiaoningLiu seguler yaxia vinjiang No follow up on this issue? I can confirm that we have plans to split the node. Apart from this, it seems a lot more can be done based on your suggestion.
XiaoningLiu vinjiang we should take these for the next planning cycle. Awesome thanks for the update seguler. Also thanks to the suggestions 1N50MN14 provided. Skip to content. Star Clifford P says:. Matt Shaw says:. April 19, at pm. Jason says:. Nikola Nikolov says:. Bob Chip says:. Aloade says:. August 4, at am.
Vineeth Pradhan says:. May 25, at am. Kennedy Nwaorgu says:. July 12, at pm. June 26, at am. Mark Truitt says:. November 1, at pm.
0コメント