npm bin
no longer works with node >= 18- Also adds detection for the new
spago.yaml
project file
- It's the better default
- It's been many years now
- Also cleans up some of the documentation and outdated links and references
- To figure out if the server isn't running we remember if the last
connection attempt failed. By triggering an explicit request (asking
for a type explicitly/go-to-definition/manual autocompletion) you
can force a re-check for an externally started server. Running
psc-ide-server-start
also resets the behaviour.
- This might mean that Windows users that use a wrapped psc-package executable will need to put the actual executable on the path
-
psc-ide-source-globs
should now only specify non-dependency source files (It's defaulted to'("src/**/*.purs" "test/**/*.purs")
) -
The plugin will now detect psc-package projects and call psc-package sources to determine what source globs to pass to the editor
-
A new
psc-ide-force-user-globs
variable was introduced to override the new behaviour and force the user specified globs
2018-05-17 Don't try to fix up temporary paths for flycheck (there shouldn't be any in the compiler output)
You can bring up the documentation for the current completion with C-h during completion
This sets the --editor-mode flag on the server executable if set to true. It defaults to false for backwards compatibility, but will default to true in a while
- Added a LICENSE file and the appropriate headers
- Fixes a bug where large responses would cause psc-ide-send-sync to fail
-
Displays completions with their already imported qualifiers. This can be toggled off with
(setq psc-ide-add-qualification-on-completion nil)
. -
Displays the result of the load command in the message buffer
- Switched to purescript-0.11 compatible
purs
executable by default. The 0.10 binaries can be regained with(setq psc-ide-use-purs nil)
, but we'll remove this switch when purescript-0.12 is released.