What is filepath?
This package provides functionality for manipulating FilePath values, and is shipped with GHC. It provides two variants for filepaths: legacy filepaths: type FilePath = String operating system abstracted filepaths (OsPath): internally unpinned ShortByteString (platform-dependent encoding) It is recommended to use OsPath when possible, because it is more correct. For each variant there are three main modules: System.FilePath.Posix / System.OsPath.Posix manipulates POSIX/Linux style FilePath values (with / as the path separator). System.FilePath.Windows / System.OsPath.Windows manipulates Windows style FilePath values (with either \ or / as the path separator, and deals with drives). System.FilePath / System.OsPath for dealing with current platform-specific filepaths System.OsString is like System.OsPath, but more general purpose. Refer to the documentation of those modules for more information. An introduction into the new API can be found in this blog post. Code examples for the new API can be found here.
filepath is a tool in the Build Automation category of a tech stack.
filepath Pros & Cons
Pros of filepath
No pros listed yet.
Cons of filepath
No cons listed yet.
filepath Alternatives & Comparisons
What are some alternatives to filepath?
NuGet
A free and open-source package manager designed for the Microsoft development platform. It is also distributed as a Visual Studio extension.
RubyGems
It is a package manager for the Ruby programming language that provides a standard format for distributing Ruby programs and libraries, a tool designed to easily manage the installation of gems, and a server for distributing them.
Bower
Bower is a package manager for the web. It offers a generic, unopinionated solution to the problem of front-end package management, while exposing the package dependency model via an API that can be consumed by a more opinionated build stack. There are no system wide dependencies, no dependencies are shared between different apps, and the dependency tree is flat.
