Ignite: IGNITE_PLUGINS_PATH shouldn't be required

Created on 3 Mar 2017  路  3Comments  路  Source: infinitered/ignite

772 introduced IGNITE_PLUGIN_PATH and required it. However, I don't really think this should be required -- we should infer the path if not found. This results in a bad DX (IMO) when first spinning up an Ignite app.

screen shot 2017-03-02 at 3 28 51 pm

discussion

Most helpful comment

I knew that.

headdesk

All 3 comments

It was only in place so we can make everything work while in dev mode. The packages will all live on npm.

Just a heads up, this message only appears when the package isn't found on npm.

The resolution order for ignite add something goes like this:

  • look for a directory called something (can be relative or absolute)
  • look for a directory called something in any path found on IGNITE_PLUGIN_PATH
  • look on npm

If all these fail you see that message.

Once we publish ignite-ir-app, we won't see this error anymore.

I knew that.

headdesk

Was this page helpful?
0 / 5 - 0 ratings