purs version to
v0.12.0 and dropped support for all
compiler versions earlier than that. (#399 and #405 by @JordanMartinez)
psa version to
v0.7.0 and dropped support for all
versions earlier than that. (#399 by @JordanMartinez)
node version to
v12.0.0 and dropped support for all
versions earlier than that. (#401 by @JordanMartinez)
devDependencies field when publishing (#405 by @JordanMartinez)
pulp publish will fail if a dependency (e.g.
exists in both the
When this occurs, you will see a message like the following:
There is a problem with your package, which meant that it could not be published. Details: The following dependency does not appear to be installed: * purescript-numbers
debug flag that enables debugger output for the
pulp publish command (#405 by @JordanMartinez)
Improve error message due to
pulp publish needing to be run twice (#406 by @JordanMartinez)
Whenever one runs
pulp publish for the first time, the command will almost always fail with
an HTTP 400 error due to invalid JSON. Running the command a second time will succeed and finish
what was started in the first one. However, this fact is never communicated to users, so
one can only handle this situation if they already know about it (e.g. aren't new users).
The error message now suggests the user try running it a second time to get around this issue.
v0.15.0compiler version (#401 by @JordanMartinez)
v0.14.0-compatible libraries. (#399 by @JordanMartinez)
pulpworks when the compiler version used is
v0.14.x. (#399 by @JordanMartinez)
mainbeing an appropriate entry point when generating a call to
main. This previously relied on a compiler-internal API (the externs.json files) which the compiler no longer produces as of v0.13.8. Note that previous versions of Pulp can work around this bug by passing the
--no-check-mainflag. (#392, @garyb).
purs >= 0.13.0in
pulp docs. Because of idiosyncrasies in the previous
purs docsCLI, it has not been possible to support both, so support for
purs < 0.13.0in
pulp docshas been dropped.
pulp docs; now that html is the default output format of
purs docs, it makes less sense to only produce local modules by default (since if we don't produce dependency modules then links will be broken). To restore the previous behaviour, you will need to run
pulp docs -- --format markdown, and then manually delete non-local modules from the
pulp docs; to be passed to
purs >= 0.13.0, since
purs docsnow uses a compiler output directory.
pulp browserifyon node 12.x (#380, @rnons).
gazeto follow symlinked directories (#378, @rnons).
pulp publish, which were both completely broken as of changes in v12.4.1 (@hdgarrood)
pulp server; this fixes an issue where if you have source files which are symbolic links which point outside your source directory, changes to those files would not be picked up (@rnons, #371)
pulp publishwould fail for packages which do not have any dependencies (@hdgarrood)
--source-mapsoption with a new
pulphas now been made aware of this and so generating source maps should now work (with compilers from both before and after this change). (@nwolverson, #343)
pulp initgenerate projects based on compiler version: the
pulp initcommand now has the ability to produce a project skeleton using either
Eff. By default,
Effectis chosen if the compiler version is at least 0.12.0, otherwise
Effis chosen. However, this behaviour can be overridden with the
pulp init. (#340, @vladciobanu)
Effect.Effectis now considered by Pulp to be acceptable for the type of your program's entry point (usually
Control.Monad.Eff.Effalso continues to be acceptable. (#338)
pulp versionfor the first time. (@plippe, #328)
pulp runnow go to your program, as the documentation claims, rather than to
purs. (@kika, #309)
pulp browserify --standalone, since there is no reason to do so. (#339)
--watchwould sometimes produce an internal error (@thoradam, #300).
mainis required to be of type
Eff, but this can be controlled using the
--check-main-typeflag. Alternatively this check can be turned off entirely using the
--elseoption (@tkawachi, #294)
pulp versionin a repo which didn't yet have any git tags would cause pulp to crash
--includeoption (@anilanar, #263)
pulp server(@geigerzaehler, #288)
Nothing changed this release, I just messed up the 10.0.2 release so published another patch-level update.
psc(or whichever underlying program
pulpcalls) has turned out to be confusing. Instead, passthrough arguments are now separated from pulp's arguments with a
--. Any unrecognised arguments before the
--will now cause pulp to complain.
pulp serverhas been broken since 9.0.0 and is now fixed! It also no longer uses webpack and purs-loader, instead it builds with the same mechanisms that
pulp builduses, which should make things more reliable and easier (#151). This is a breaking change because some command line options for
pulp serverwere removed as they were webpack-specific and therefore no longer applicable.
pulp runwhich were not applicable and should never have been there:
pulp dephas been deprecated for quite a long time now.
--jobsfor specifying parallelism in
pulp init(#231). Now, pulp delegates to
bower install --saveto select an appropriate version range.
pulp init(@texastoland, #223, 225).
pulp initto pick up the newest versions of core libraries (@Risto-Stevcev, #230).
npm install pulp.
bower uninstallinstead of the undocumented and presumably deprecated
bower rm(@menelaos, #215).
watchpackto fix deprecation warnings (#196).
pulp publish, allowing you to skip pushing tags to a Git remote as part of publishing (#201).
pulp publish, allowing you to push to a specific Git remote (#201).
pulp login(which was still broken).
moduleTypefield from the bower.json file generated by
pulp loginusing the wrong environment variable for the home directory on Windows (#197).
pulp loginfailing to check the auth token with GitHub (#199).
pulp versionfor bumping versions and creating git tags for releases of PureScript packages, as well as
pulp publishfor sending those releases out into the world. See
pulp version --helpand
pulp publish --helpfor more info.
pulp browserifyhanging on Windows.
--monochromeoptions not being honoured when using psa.
pulp login, which will be useful later along with the upcoming
--forceflag is now once again only available on
pulp browserify, to force a non-incremental build.
psatool instead of
pscif available on your path. You can disable this behaviour by passing the
Bugs fixed: #140.
--engineoption, since the
--runtimeoption fulfils the same need.
--runtimeoption, which was previously broken. (#143)
pulp psci, so that long-running commands can be interrupted, and to stop the "hGetChar: hardware fault (Input/output error)" message from being shown. (#88)
--watchoption, which was broken in 6.2.0.
pulp server, since it doesn't really make sense with these commands.
pulp depis now deprecated. It continues to work as before, but you will have to install Bower yourself in order to use it. It’s recommended that you use Bower directly instead.
--skip-entry-pointnow works when using
pulp build --to.
pulp browserify --standalone <module-name>to produce a browserified bundle wrapped in a UMD header, which can be
require()d, and which re-exports the main module of your PureScript project. It works by invoking
browserify --standalone; see the Browserify documentation.
Pulp has been ported to PureScript :)
--with-deps flag for
pulp docs has been renamed to
Bugs fixed: #123, #122, #121, #111, #108, #92.
Bugs fixed: #109.
Bugs fixed: #105, #106, #107, #113.
Pulp will now skip the build step if your project hasn't changed since your last rebuild.
--force flag is now avaliable on all commands that trigger a
build, and will force a rebuild regardless of whether your project
has changed. It still also forces a non-incremental build when
You can now use the flags
--dependency-path to override the normal locations for these
The format for passing multiple directories to
changed: you now separate directories using the standard system path
delimiter, as opposed to spaces.