David Burles

:+1:

Hey guys. Looking to get some discussion going again on updating this package, or potentially also looking at other approaches to adding semantic-ui to Meteor. cc @levithomason.

Also worthy to note; this package was developed before Meteor had proper support for npm packages. That was introduced in 1.3.

Hey @levithomason are you able to share your bash script?

Thanks @levithomason! It really illustrates how specific of a configuration Meteor requires.

That sounds like an ideal solution to me!

There will also need to be a way to expose errors that are explicitly thrown, such as argument validation messages etc.

I think a good solution might be to check for the presence of an `expose` property on the error object. Also, `status` would be great too, so users can set...

> Those should not be thrown but instead the execute/validate functions should return the corresponding errors, or what are you referring to? I mean just validation like: ```js resolve(obj, {...

Right, I think I see what you're saying. These errors won't be affected by your [proposed changes](https://github.com/contrawork/graphql-helix/issues/77#issuecomment-950303919) and they can be handled independently.