Sam Verschueren
Sam Verschueren
Add possibility to extend the configuration with the `extends` option like [ESLint](http://eslint.org/docs/user-guide/configuring#extending-configuration-files).
I used `ZSchema` to validate `package.json` based on a JSON schema. Apparently something changed under the hood and the error messages totally broke. Disabled the tests for now.
I never use lockfiles for my modules, only for applications to make sure that the application that is built has the exact same dependencies as the one I tested everything...
There's something wrong with `lintspaces` on windows, it doesn't correctly pick up the config file.
We now also support the nvm aliases `lts/argon` (Node.js 4) and `lts/boron` (Node.js 6). Currently the `travis` rule does not prevent something like this. ```json { "name": "my-module", "engines": {...
Currently the user has to add `babel-preset-env` every single time. Should we bake this in and provide good defaults? I think it's always good to have good defaults.
They're working on it to bring that functionality via an API so we can use that. But it's not possible at the moment though.
When I run the updater, this is the error that is logged in the debugger. ``` Starting debug for 'Packal Updater' [2016-07-12 16:31:40][STDERR: input.scriptfilter] mkdir: /Users/sam/Library/Caches/com.runningwithcrayons.Alfred-2/Workflow Data: No such file...
Hi 👋 . Thanks for this plugin, it's very useful! I noticed that when parsing the following import statement, the plugin fails. ```ts import test from 'test.json' with { type:...