When comparing NPM vs Inkscape, the Slant community recommends NPM for most people. In the question“What are the best web design tools?” NPM is ranked 3rd while Inkscape is ranked 5th. The most important reason people chose NPM is:
NPM is compatible with any CLI the developer wants to use.
Ranked in these QuestionsQuestion Ranking
Pro Compatible with any CLI
NPM is compatible with any CLI the developer wants to use.
Pro Plenty of helpful NPM modules/plugins
NPM has a strong community that has developed plenty of libraries and plugins that are useful to developers.
Pro Very concise configuration
NPM scripts require fewer lines of code to run a given task. This is true even when it's for running build processes. Using Unix pipes lots of tasks can be reduced to one-liners.
Pro Does not need any wrapper modules
With other task runners, you need to install wrapper modules for tools you may already have installed. When using NPM that's not necessary, to use the tools you need, just install them directly through NPM.
Pro Part of node.js distribution
Pro You're most likely using NPM already
Pro Uncomplicated package management system
When it works...
Pro Free and open source
Inkscape is GPL-licensed and maintains public repositories.
Pro Opens lots of file types
Inkscape supports many common formats for import (including SVG, Photoshop and Illustrator) and its plugin architecture allows more to be added.
Pro Export to different file types
You can export and save your files for example as a "normal" svg, png, jpg, bmp etc. file.
Pre-built binaries are available for Windows, Mac and Linux. Inkscape can be built from source on additional platforms.
Pro Dark Theme Support
The new 1.0 beta 2 version finally got support for dark theme which normally is only available for commercial software like Affinity Serif, Adobe Illustrator.
Pro It can do anything
A very powerful software that can do pretty match anything!
Pro Integrates well into a X11-System
Its uses the X11 icon theme and desktop theme(GTK).
Pro Measurement Tool
This tool is extremely handy and I was not able to find it in any other vector graphics programs out there.
Pro Live Path Effects
Extremely powerful menu that offers more than 30 powerful Live Path Effects to apply to your paths vastly enhancing the application functionality.
Pro Guides, Grids, and Canvas Rotation
Extremely handy features when building complex graphics using Inkscape.
Pro Interface is available in 29 languages
Basque, British English, Brazilian, Portuguese, Catalan, Croatian, Czech, Dutch, Finnish, French, German, Greek, Hindi, Hungarian, Icelandic, Indonesian, Italian, Korean, Latvian, Norwegian (Bokmål), Polish, Romanian, Russian, Slovak, Spanish, Swedish, Turkish, Ukrainian, Urdu, Swedish.
Pro It's really easy and fun
You can edit and create vector graphics with Inkscape.
Con Custom tasks require additional keyword 'run'
Only a few standard tasks support being executed without the
run keyword (e.g.,
npm start vs
npm run customtask)
Con Not a build system, only a task runner
It is supposed to be used for running gulp, webpack or whatever. But it is not supposed to be used as a build system.
Con Passing parameters is awkward
In order to pass additional parameters to npm you must add them after
npm run build -- --custom='foo').
Con Badly documented
Less than bare minimum official documentation leaves users in the dark without taking often expensive external courses. Even the --help text has unpluggable gaps. One official source notes the documentation isn't adequate yet nothing has been done to fix this.
Con Lot of issues with authentication and random node problems
Unable to recover from common depencies conflicts consistantly. Error messages are not always helpful to debugging. Doesn't account well for users with different versions of node.
Con Does not run well with Windows
Since a lot of projects that use NPM as a build tool most of the time make use of Bash scripts as well. This means that open source projects that run the command
npm run may run into issues when used in a Windows environment.
Con Doesn't allow you to create build process with complicated logic on its own
In complex heterogeneous app you will quickly migrate to gulp, webpack or whatever leaving to NPM only simple task running responsibility.
Con Very slow startup on some systems
Depending on factors like how many fonts you have installed, Inkscape can take upwards of 30 seconds to launch.
Con Uses its own SVG-format by default
Inkscape might use SVG as its default format, however this SVG's contains some additional SodiPodi/Inkscape additions that can be troublesome if you want to import the SVG into some other application.
Con Mac version does not look as polished as its versions for Windows/Linux version for the 0.92.x version
It seems that Inkscape 1.0 beta 2 for Mac got some needed attention and it looks a lot better with dark theme support. native DMG installer and they got rid of X11 which is great.
Con Based on the GTK widget toolkit
Software is based on GTK, so it might not integrate well in non-GTK environments. It also requires many dependencies on those non-GTK desktops. It also adds dependencies to GTK-environments since it is written in C++ which requires the gtkmm wrapper/interface.
Application is often buggy so it happens from time to time that the popup / right-click menu won't close and stays open. It crashes also sometimes randomly. This makes it almost unusable for productive / business use.
Con Incompatible with previous versions
Sometimes backward compatibility breaks. For example, pre 0.92 SVGs are incompatible with later releases (due different default resolutions).
Con Crashes very often
Inkscape encountered an internal error and will close now - is one of its standard messages.
Con 1.0 is sluggish
Inkscape 1.0 uses GTK 3 which is sluggish and slow for low spec systems( eg. ARM, Celeron, Pentium, Core-i3, Ryzen 3 or Athlon ) compared to previous versions.
Con Limited work with ICC CMYK color scheme
Support for ICC color profiles only in SVG files.
Con Since 0.91 the gradient editor is gone
It is now only possible to edit a gradient on screen. but you can't set a stop to a specific percentage anymore.
Con Y-axis inverted
0,0 coordinates begin in lower left corner, not upper left corner as SVG standards define in Inkscape 0.92.x.
It seems this is now fixed in the 1.0 beta 2 version of the program.
Con No support for large printing machine system
No support for large printing machine environment, except exporting the resulting artwork to PDF.
Con Under GNU GPL
It is released under GNU GPL which one of the restricted open source license.