You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi - firstly, thanks for the work on this - it looks like it will be a very useful library for us.
I am trying to get it running with jspm - which like browserify has issues with the require.resolve. I have sorted this for aesprim.js by just including the modified version of the library instead (not perfect but does the trick for now).
With grammar.js it does not appear that the moduleInclude: & actionInclude: parameters that use require.resolve are used anywhere currently - are these historical, or there for future use, or am I just overlooking their purpose? Some basic testing seems to indicate that things work ok without these properties, but would be good to know what is likely to break without them.
Thanks
Glen
The text was updated successfully, but these errors were encountered:
Hi - firstly, thanks for the work on this - it looks like it will be a very useful library for us.
I am trying to get it running with jspm - which like browserify has issues with the require.resolve. I have sorted this for aesprim.js by just including the modified version of the library instead (not perfect but does the trick for now).
With grammar.js it does not appear that the moduleInclude: & actionInclude: parameters that use require.resolve are used anywhere currently - are these historical, or there for future use, or am I just overlooking their purpose? Some basic testing seems to indicate that things work ok without these properties, but would be good to know what is likely to break without them.
Thanks
Glen
The text was updated successfully, but these errors were encountered: