| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Extract deps path
* Initial psc-package support
* index.js: `pscPackage` and `src` incompatibility warning
* index.js: make use of user-provided options
* index.js: make use of user-provided options: now for pscIdeColors
* index.js: remember depsPaths call result
* index.js: implemented appending user src paths with psc-packages'
* README.md: sync changes of pscPackage behavior
Also reflect pscPackage support in "Default options" section
|
| |
|
|
|
|
| |
Avoids duplication of warnings. Resolves #78
|
| |
|
|
|
|
|
|
|
| |
Instead of forcing a recompile on an unknown value and on unknown module
imports, opt to only recompile for unknown module imports. An unknown
value may be a typo. Having a faster feedback loop in these cases seems
ideal.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The objective of enabling psc-ide is to obtain feedback immediately from
the PureScript compiler. When the loader triggers an error to webpack,
the bundle is invalidated and dependencies of the PureScript file that
caused the error will be passed through the loader on the next
successful rebuild.
However, this behaviour adds time to the feedback loop. In order to
reduce the time of the PureScript compiler feedback loop when in
development, this commit always resolves the rebuild process with a
success. Errors and warnings are still emitted, but the webpack bundle
is not invalidated. This means that the loader will only be run for the
current file being editted and the developer gets immediate feedback on
success or failure when psc-ide is enabled.
Resolves #76
|
| |
|
|
|
|
| |
See issue #69
|
| |
|
| |
|
|
|
|
| |
Resolves #57
|
|
|
|
| |
Resolves #58
|
|
|
|
| |
Resolves #59 and resolves #60
|
|
|
|
|
|
|
|
|
| |
Adds support for PureScript 0.9.1 and newer (purescript/purescript#2151)
The `next` tag on NPM points to this pre-release. Also note that
`peerDependencies` has been removed (npm/npm#8854).
Resolves #54
|
|
|
|
| |
Resolves #52
|
|
|
|
| |
Resolves #50
|
|
|
|
|
|
|
| |
Attach a handler to the `psc-ide-client` process to capture one or more
chunks from the `data` event.
Resolves #48
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Using psc-ide-server is experimental and there may be bugs or edge-cases.
|
| |
|
|
|
|
|
|
|
| |
- Remove dependence on purescript-webpack-plugin
- Fixes double-compilation issue by loading compiled JS instead of adding
dependency.
- Uses `psc-ide-server` for fast rebuilds.
|
|
|
|
| |
Resolves #41
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| | |
Resolves ethul/purescript-webpack-plugin#9
|
|/
|
|
| |
Resolves #40
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
The module file path and dependency graph information is provided by the
purescript-webpack-plugin.
Resolves #37
|
| |
|
|
|
|
|
|
|
|
| |
The loader creates shim modules that reference their corresponding
PureScript module that is bundled by the PureScript webpack plugin,
which invokes `psc` and `psc-bundle`.
Resolves #31 and resolves #32
|
| |
|
|
|
|
|
|
|
|
| |
Fixes #15
Removes the `require-path` option and fixes it to '../'. When generating
the temporary module for Webpack, use a relative path to the output
directory so it doesn't need to be in `modulesDirectories`.
|
|
|
|
| |
Resolves #28
|
|
|
|
| |
Resolves #26
|
| |
|
| |
|
|
|
|
| |
Resolves #24
|
|
|
|
| |
Resolves #18
|
|
|
|
| |
Resolves #17
|
|
|
|
| |
Resolves #11
|
|
|
|
| |
Resolves #14
|
|
|
|
|
|
|
|
|
|
|
| |
Adds the `psc-make` options `comments` and `no-prefix`. Also, an
internal option `src` has been added that is used to specify the source
paths of `PureScript` files that will be globbed for compilation.
By default the `bower_components` path is globbed, but the loader
requires that the source paths be provided for the user's code.
Resolves #12
|
|
|
|
|
|
|
| |
Improving the generation of the dependencies in `mkDeps` to avoid a
`RangeError` on large inputs.
Resolves #9
|