search

gulpjs / rechoir

Prepare a node environment to require files with different extensions.
MIT License
48 stars 12 forks source link

Fix for #6 #9

Closed silkentrance closed 9 years ago

silkentrance commented 9 years ago
silkentrance commented 9 years ago

I am waiting for #16 to be merged to continue working on this one.

silkentrance commented 9 years ago

@tkellen please have a look, tests are passing and user can now provide a custom node-interpret.js to integrate additional languages on the fly.

Documentation requires some more work though.

phated commented 9 years ago

What about using https://www.npmjs.com/package/rcfinder and naming the file .interpretrc? Also, we should probably depend on https://www.npmjs.com/package/extend/https://www.npmjs.com/package/xtend or node's util._extend instead of writing and maintaining our own.

silkentrance commented 9 years ago

@phated

extend: i'd favor node's built in extend function, thanks for pointing this out

Hidden files: I am not really comfortable with hidden files in my repositories unless they serve a purpose other than runtime, e..g supporting the build process.

See also https://github.com/tkellen/node-rechoir/issues/6#issuecomment-68534617 and https://github.com/tkellen/node-rechoir/issues/6#issuecomment-68534819 where @tkellen and I discussed about hidden files vs non hidden files.

phated commented 9 years ago

As per https://github.com/tkellen/node-rechoir/issues/6#issuecomment-74392988

silkentrance commented 9 years ago

@phated this is still a viable option for incorporating additional languages/extension aliases on the fly. reopening.