-
Notifications
You must be signed in to change notification settings - Fork 219
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
Unused dependancy: brfs #45
Comments
The problem is that it's required for browserify builds. Moving it to devDependencies would require the user to know to install brfs along with fontkit, or whatever required fontkit. |
Perhaps it could be moved to |
note that if it's in devDependencies, it will still get automatically installed during an |
@Pomax only if you are running |
ah, right. |
For brotli.js I managed to get rid of brfs by writing a base64 JS string version of the binary file and using |
Currently, not only |
It would also help fix the |
All this talk about chopping off large chunks of depedencies makes me happy. It'd speed up Wakamai Fondue considerably. E.g. I'd only need Brotli to decompress fonts, not to compress them. In other words, +1 |
Unfortunately, all of those dependencies are still required. They are used for builds using browserify. |
@RoelN what part would it speed up, though? The runtime should not be noticably affected by the dependency. |
Having real touble with this, npm install pdfkit --only=prod is kicking this back as a vulnerbility. From what I understand this shouldn't even be installed. Am I doing something wrong? Same issue on linebreak too. |
@devongovett Is this statement strictly true? I thought it depended upon the value of NODE_ENV. Please see my previous comment |
@awerlang thanks, I read that and tried several permutations but I am still seeing this included when installing the downstream package (pdfkit). This fails |
@Pomax I meant in package size, reducing download time. I don't expect any real difference in runtime. |
Brfs is a very large module. Could it be moved to devDependancies if possible?
The text was updated successfully, but these errors were encountered: