Downloads:
6,556
Downloads of v 0.13.4:
187
Last Update:
21 Oct 2019
Package Maintainer(s):
Software Author(s):
- The Purescript community
Tags:
purescript haskell javascript typed-language alt-js- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
purescript
This is not the latest version of purescript available.
- 1
- 2
- 3
0.13.4 | Updated: 21 Oct 2019
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
6,556
Downloads of v 0.13.4:
187
Maintainer(s):
Software Author(s):
- The Purescript community
purescript 0.13.4
This is not the latest version of purescript available.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
Deployment Method: Individual Install, Upgrade, & Uninstall
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:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
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 https://community.chocolatey.org/api/v2/. 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
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download purescript --internalize --version=0.13.4 --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade purescript -y --source="'INTERNAL REPO URL'" --version="'0.13.4'" [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="'INTERNAL REPO URL'" --version="'0.13.4'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install purescript
win_chocolatey:
name: purescript
version: '0.13.4'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'purescript' do
action :install
source 'INTERNAL REPO URL'
version '0.13.4'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller purescript
{
Name = "purescript"
Version = "0.13.4"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'purescript':
ensure => '0.13.4',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. 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 21 Oct 2019.
A small strongly typed programming language with expressive types that compiles to JavaScript, written in and inspired by Haskell.
Log in or click on link to see number of positives.
- purescript.0.13.4.nupkg (916fccbba8e2) - ## / 59
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.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
purescript 0.15.8 | 167 | Monday, March 13, 2023 | Approved | |
purescript 0.15.7 | 50 | Tuesday, January 3, 2023 | Approved | |
purescript 0.15.6 | 58 | Wednesday, November 9, 2022 | Approved | |
purescript 0.15.4 | 57 | Thursday, September 8, 2022 | Approved | |
purescript 0.15.3 | 69 | Friday, June 24, 2022 | Approved | |
purescript 0.15.2 | 69 | Thursday, May 19, 2022 | Approved | |
purescript 0.15.0 | 56 | Tuesday, May 3, 2022 | Approved | |
purescript 0.14.7 | 68 | Monday, February 28, 2022 | Approved | |
purescript 0.14.5 | 95 | Wednesday, November 17, 2021 | Approved | |
purescript 0.14.4 | 97 | Thursday, August 26, 2021 | Approved | |
purescript 0.14.3 | 94 | Thursday, July 8, 2021 | Approved | |
purescript 0.14.2 | 104 | Monday, June 14, 2021 | Approved | |
purescript 0.14.1 | 101 | Tuesday, April 20, 2021 | Approved | |
purescript 0.14.0 | 115 | Monday, March 1, 2021 | Approved | |
purescript 0.13.8 | 275 | Wednesday, May 27, 2020 | Approved | |
purescript 0.13.6 | 387 | Monday, January 20, 2020 | Approved | |
purescript 0.13.5 | 173 | Thursday, November 14, 2019 | Approved | |
purescript 0.13.4 | 187 | Monday, October 21, 2019 | Approved | |
purescript 0.13.3 | 168 | Monday, August 19, 2019 | Approved | |
purescript 0.12.5 | 362 | Monday, April 15, 2019 | Approved | |
purescript 0.12.4 | 187 | Friday, April 12, 2019 | Approved | |
purescript 0.12.3 | 341 | Tuesday, February 26, 2019 | Approved | |
purescript 0.12.1 | 269 | Wednesday, November 14, 2018 | Approved | |
purescript 0.12.0 | 330 | Friday, June 29, 2018 | Approved | |
PureScript 0.7.4.1 | 726 | Monday, August 31, 2015 | Approved | |
PureScript 0.7.3 | 443 | Monday, August 17, 2015 | Approved | |
PureScript 0.7.2 | 460 | Wednesday, August 5, 2015 | Approved | |
PureScript 0.7.1 | 434 | Friday, July 31, 2015 | Approved | |
PureScript 0.6.9.3 | 614 | Thursday, March 19, 2015 | Approved |
Enhancements
Use content hashes when determining whether a file needs rebuilding (#3708, @hdgarrood)
We now calculate and store content hashes of input files during compilation. If a file's modification time has changed since the last compile, we compare the hash to the previous hash; if the hash is unchanged, this allows us to skip rebuilding this file, speeding up the build.
Include import declaration qualifiers in unused import warnings (#3685, @matthew-hilty)
Previously, warnings didn't distinguish between import declarations from the same module. Code like the following
import A.B (x) -- `x` is used. import A.B (y) as C -- `y` is not used.
would induce a warning like
The import of module A.B is redundant
even though only the qualified import declarationC
is actually redundant. The warning now would beThe import of module A.B (qualified as C) is redundant
.Include kind imports when determining unused import warnings (#3685, @matthew-hilty)
Previously, kind imports were ignored. The linter wouldn't emit any warnings for code like the following.
import A.B (kind K) -- `kind K` is not used.
And the linter, disregarding
kind K
, would emit anUnusedImport
instead of anUnusedExplicitImport
for code like the following.import A.B (x, kind K) -- `x` is not used, but `kind K` is.
Better reporting of I/O errors (#3730, @hdgarrood)
If an unexpected I/O error occurs during compiling, we now include details in the error message. For example, when trying to write compilation results onto a device which has run out of space, we previously would have received a "CannotWriteFile" error with no further information. Now, we receive the underlying error message too:
I/O error while trying to write JSON file: ./output/cache-db.json ./output/cache-db.json: hClose: resource exhausted (No space left on device)
Bug fixes
Improve type class resolution in the presence of constrained higher-order functions (#3558, @matthew-hilty)
This is perhaps best illustrated with an example.
newtype LBox row a = LBox (∀ r. (∀ lbl _1. Row.Cons lbl a _1 row ⇒ IsSymbol lbl ⇒ SProxy lbl → r) → r) unLBox ∷ ∀ row a r. (∀ lbl _1. Row.Cons lbl a _1 row ⇒ IsSymbol lbl ⇒ SProxy lbl → r) → LBox row a → r unLBox g (LBox f) = f g read ∷ ∀ row a. Record row → LBox row a → a read rec = unLBox \\lbl → Record.get lbl rec
The
read
function would previously fail with the errorNo type class instance was found for Prim.Row.Cons lbl4 a5 t2 row6
although that dictionary should have been available in the function passed to
unLBox
. Now, it type checks successfully.Fix cache invalidation false negatives by storing timestamps (#3705, @hdgarrood)
Previously, an input file would be considered 'modified', and thus requiring rebuilding on a subsequent compile, if its modification time specifies a point in time after any of the modification times of the corresponding output files. This has turned out to be insufficient; files can often change in a way that this algorithm misses, because the input file might still have a timestamp older than the output files. Often this can happen by switching between
git
branches or by updating a dependency.This problem can manifest as compiler errors which don't appear to make sense or correspond to what is inside a source file, and which (until now) would need to be fixed by a clean rebuild (e.g.
rm -r output
).We now make a note of the modification time when we read an input file, and we consider that input file to have changed on a subsequent compile if the modification time is different to what it was before.
The hope with this fix is that it should never be necessary to remove an output directory to get a build to run successfully. If you do run into this problem again, it is a bug: please report it.
Fix exports incorrectly being identified as unused in purs bundle (#3727, @rhendric)
References to properties on the
exports
object would previously not be picked up bypurs bundle
as uses of those properties, which could lead to them being incorrectly removed. For example:'use strict'; exports.foo = 1; exports.bar = exports.foo;
would remove the
exports.foo = 1;
statement, breaking the assignment toexports.bar
, iffoo
were not used elsewhere. This statement is now no longer removed.Show entire rows in type errors in the presence of the
--verbose-errors
flag (#3722, @Woody88)The row diffing feature, which elides common labels in rows occurring in type errors, did not previously respect the
--verbose-errors
flag, giving the same output regardless of whether it was set or not. Now, if the flag has been supplied, we always show the entire row.
Other
Add Makefile command to run license generator (#3718, @hdgarrood)
Update language-javascript to 0.7.0.0 (@rhendric, @hdgarrood)
This enables a number of newer JavaScript syntactic constructs to be used in FFI files. Please see the language-javascript release notes for details.
Fix for object shorthand syntax in FFI files (#3742, @hdgarrood)
This package has no dependencies.
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.