Separating repo?

[drewhamlett]

I'd like to use js-beautify as git submodule but I hate to pull down php and python code too.

Considering this is JS beautify, would it make any sense to put the JS version in it's own repo? Then call other ones like js-beautify-php js-beautify-python. Basically I'd like to have the JS versions of the beautify(JS, HTML, CSS)

Just a thought.

[einars]

I really care for and maintain only js and python versions, it looks to me that by separating the repos they quickly and easily would to run out of sync (now in case of problems/bugs/etc I fix them both simultaneously).

Maybe a separate js-only branch with a semi-automatic export of the lib, something like it's currently done with gh-pages push 💡

[drewhamlett]

Semi-automatic export JS-only branch sounds great to me. Just thought I'd pass it by you. I'd hate to have people rely on me to manually keep up with changes in JS-beautify in the brackets-beautify project. Thanks.

[einars]

adding a cross-reference to #181, where the need for tagged release packages was mentioned

[evocateur]

If you depend on https://npmjs.org/package/js-beautify, you'll only download the JS (achieved through liberal use of .npmignore, which omits the Python and PHP from the npm artifact).

[bitwiseman]

@drewhjava - It looks like @evocateur is keeping this version of the npm package up-to-date, and it only has the javascript in it. Will that be sufficient? Can we close this issue?

[drewhamlett]

@bitwiseman @evocateur Ok cool. That looks like it will work. Thanks for the help!

[drewhamlett]

@evocateur @bitwiseman Actually, now that look at it, the npm version doesn't have the html and css beautify files.

This one includes html and css but is not updated regularly.

https://npmjs.org/package/beautifier

I mean maybe it's not a huge deal. I just notice js-beautify gets updated regularly and I hate to leave users in the dark.

[bitwiseman]

@drewhjava - Please open a new issue for this, either here or in @evocateur 's awesome fork https://github.com/evocateur/js-beautify , since he's running the show for npm packaging.

[evocateur]

@drewhjava Sorry, I had Issues disabled in my fork. I've re-enabled them, and will be opening an issue shortly.