Downloads of v 0.12.4:


Last Update:

12 Apr 2019

Package Maintainer(s):

Software Author(s):

  • The Purescript community


purescript haskell javascript typed-language alt-js


This is not the latest version of purescript available.

  • 1
  • 2
  • 3

0.12.4 | Updated: 12 Apr 2019



Downloads of v 0.12.4:


Software Author(s):

  • The Purescript community

  • 1
  • 2
  • 3
purescript 0.12.4

This is not the latest version of purescript available.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


To install purescript, run the following command from the command line or from PowerShell:


To upgrade purescript, run the following command from the command line or from PowerShell:


To uninstall purescript, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade purescript -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade purescript -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure purescript installed
    name: purescript
    state: present
    version: 0.12.4
    source: STEP 3 URL

See docs at

chocolatey_package 'purescript' do
  action    :install
  version  '0.12.4'
  source   'STEP 3 URL'

See docs at

    Name: purescript,
    Version: 0.12.4,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller purescript
   Name     = 'purescript'
   Ensure   = 'Present'
   Version  = '0.12.4'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'purescript':
  provider => 'chocolatey',
  ensure   => '0.12.4',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install purescript version="0.12.4" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 12 Apr 2019.


A small strongly typed programming language with expressive types that compiles to JavaScript, written in and inspired by Haskell.

$ErrorActionPreference = 'Stop';

$version     = $env:chocolateyPackageVersion
$packageName = $env:chocolateyPackageName
$url64       = ("{0}/win64.tar.gz" -f $version)

$packageArgs = @{
    packageName    = $packageName
    unzipLocation  = Split-Path $MyInvocation.MyCommand.Definition
    url64bit       = $url64
    checksum64     = "472d3f397912eb11265a0a413534f2a5d1a5df85"
    checksumType64 = "sha1"

Install-ChocolateyZipPackage @packageArgs
$File = Get-ChildItem -File -Path $env:ChocolateyInstall\lib\$packageName\tools\ -Filter *.tar
Get-ChocolateyUnzip -fileFullPath $File.FullName -destination $env:ChocolateyInstall\lib\$packageName\tools\

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
purescript 0.14.2 34 Monday, June 14, 2021 Approved
purescript 0.14.1 44 Tuesday, April 20, 2021 Approved
purescript 0.14.0 46 Monday, March 1, 2021 Approved
purescript 0.13.8 197 Wednesday, May 27, 2020 Approved
purescript 0.13.6 314 Monday, January 20, 2020 Approved
purescript 0.13.5 109 Thursday, November 14, 2019 Approved
purescript 0.13.4 106 Monday, October 21, 2019 Approved
purescript 0.13.3 98 Monday, August 19, 2019 Approved
purescript 0.12.5 275 Monday, April 15, 2019 Approved


[purs ide] Treat module declarations like any other (#3541)

This means we can now complete module names with the completion API as well as being able to query for module level documentation and goto-defintion for module names.

The list loadedModules command has also been deprecated, since you can now use the completion command with a filter for modules instead. (@kRITZCREEK)

Truncate types in errors (#3401)

Large types in error messages are now truncated. For example:

module Main where

data Id a = Id a

foo :: Id (Id (Id (Id (Id Int))))
foo = "hi"

now produces

  Could not match type
  with type
    Id (Id (Id (... ...)))

The previous behaviour of printing the types in full may be recovered by passing the --verbose-errors flag to the compiler. (@hdgarrood)

Don't generate unused imports in JavaScript output (#2177)

In both CommonJS compiler output and JavaScript purs bundle output, we no longer emit JS imports for modules whose use sites have all been optimized out. This reduces the number of warnings produced by other JavaScript bundlers or compressors such as "Side effects in initialization of unused variable Control_Category". (@rhendric)

Simplify purs publish resolutions format (#3565)

The format for resolutions files passed via the CLI to purs publish has been simplified. A new-style resolutions file should look something like this:

  "purescript-prelude": {
     "version": "4.0.0",
     "path": "bower_components/purescript-prelude"
  "purescript-lists": {
     "version": "6.0.0",
     "path": "bower_components/purescript-lists"

The version field is used for generating links between packages on Pursuit, and the path field is used to obtain the source files while generating documentation: all files matching the glob "src/**/*.purs" relative to the
path directory will be picked up.

The version field is optional, but omitting it will mean that no links will be generated for any declarations from that package on Pursuit. The "path" field is required.

The old format is still accepted, but it has been deprecated, and purs publish will now produce a warning when consuming it.

This change allows us to work around a bug in Bower which prevented packages with larger dependency trees (such as Halogen) from being uploaded to Pursuit ( (@hdgarrood)

Improve error messages for cycles in type class declarations (#3223)

A cycle in type class declarations, such as

class C a <= D a
class D a <= C a

now produces a more informative error, which no longer confusingly refers to type synonyms, and which displays all of the classes involved in the cycle. (@Saulukass)

Bug fixes

  • Naming a constructor PS no longer causes JS runtime errors when using purs bundle (#3505, @mhcurylo)
  • purs publish now warns instead of failing if not all dependencies have a resolved version, e.g. if some have been installed via a branch or commit reference instead of a version range (#3061, @hdgarrood)


  • Raise upper bound on aeson in package.yaml (#3537, @jacereda)
  • Add Nix test dependencies to stack.yaml (#3525, @jmackie)
  • [purs ide] Represent filters as a data type rather than functions (#3547, @kRITZCREEK)
  • Carry data constructor field names in the AST (#3566, @garyb)
  • Convert prim docs tests to use tasty (#3568, @hdgarrood)
  • Bump bower version used in tests (#3570, @garyb)
  • Add tests for purs bundle (#3533, @mhcurylo)
  • Update to GHC 8.6.4 (#3560, @kRITZCREEK)
  • Rerun some of the compiler tests to test with purs bundle (#3579, @rhendric)
  • Fix handling of directive prologues like "use strict" in purs bundle (#3581, @rhendric)

This package has no dependencies.

Discussion for the purescript Package

Ground Rules:

  • This discussion is only about purescript and the purescript package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or purescript, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus