strider-custom doesn't override default actions about strider-custom HOT 2 CLOSED

Here are the docs for how build hooks work:

https://github.com/Strider-CD/strider-extension-loader#build-hooks

For node.js, the simple worker has a single conditional build hook by default. Because real-world projects can have quite a number of build hooks for each phase added by numerous plugins, it becomes complicated to do overrides safely.

In practice, we haven't found this to be necessary.

When would running npm test be problematic? If really necessary, you could no-op this in your project.

from strider-custom.

hmmm I guess this makes sense.

On Sat, Jul 13, 2013 at 10:38 AM, niallo [email protected] wrote:

Here are the docs for how build hooks work:

https://github.com/Strider-CD/strider-extension-loader#build-hooks

For node.js, the simple worker has a single conditional build hook by
default. Because real-world projects can have quite a number of build hooks
for each phase added by numerous plugins, it becomes complicated to do
overrides safely.

In practice, we haven't found this to be necessary.

When would running npm test be problematic? If really necessary, you
could no-op this in your project.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-20922534
.

from strider-custom.