To build jQuery, you need to have the latest Node.js/npm and git 1.7 or later. Earlier versions might work, but are not supported. For Windows, you have to download and install git and Node.js. OS X users should install Homebrew. Once Homebrew is installed, run brew install git to install git, and brew install node to install Node.js. Linux/BSD users should use their appropriate package managers to install git and Node.js, or build from source if you swing that way. Easy-peasy. Special builds can be created that exclude subsets of jQuery functionality. This allows for smaller custom builds when the builder is certain that those parts of jQuery are not being used. For example, an app that only used JSONP for $.ajax() and did not need to calculate offsets or positions of elements could exclude the offset and ajax/xhr modules. Any module may be excluded except for core, and selector. To exclude a module, pass its path relative to the src folder (without the .js extension). Some example modules that can be excluded are: Note: Excluding Sizzle will also exclude all jQuery selector extensions (such as effects/animatedSelector and css/hiddenVisibleSelectors). The build process shows a message for each dependent module it excludes or includes. As an option, you can set the module name for jQuery's AMD definition. By default, it is set to "jquery", which plays nicely with plugins and third-party libraries, but there may be cases where you'd like to change this. Simply set the "amd" option: For questions or requests regarding custom builds, please start a thread on the Developing jQuery Core section of the forum. Due to the combinatorics and custom nature of these builds, they are not regularly tested in jQuery's unit test process. The non-Sizzle selector engine currently does not pass unit tests because it is missing too much essential functionality.

Does balancing a budget always equate to a government shutdown?

Can you believe federal employees are facing another government shutdown on October 1? When did closing the government become an acceptable solution to balancing the budget? We all live within constraints of managing our spending, yet wouldn’t it seems strange if we all decided to just stop and close our accounts? Our lawmakers would rather place hundreds of thousands of federal employees out of work than do what they were elected to do — handling our nation’s business and pass a budget.

As it stands now, Congress needs to agree to funding the government by Sept. 30, but they are way behind in passing the series of spending bills necessary to pass a full budget. Instead, lawmakers will probably try to pass a short-term budget extension that basically keeps spending levels the same as last year and keeps the government open. In fact, the cost of shutting down the government far outweighs the cost of restarting the government or allowing feds to continue to work in order to keep this country moving forward.

Haven’t we learned yet that federal employees are vital to this country’s business, both domestic and international? Take a look at how “Federal workers keep America running.” While most of the economy will be impacted negatively by a government shutdown, in fact, we could never completely shut down the government. Some federal workers were considered “exempt” from shutting down due to the nature of their jobs and place on unpaid furlough. In the 2013 shutdown, about 800,000 of the 2.1 million non-postal Executive Branch employees were furloughed without pay. The rest continued working, some without pay, but guaranteed that eventually they would be paid. This is a disappointment and a disrespectful way of showing appreciation for federal workers.

FEW is requesting that all federal workers contact their Congressman now. It’s not too late to remind them to protect America by allowing federal workers to stay on the job. We should always have a contingency plan, but its purpose should be to keep America running 100% of the time.   Use FEW’s Capwiz site to contact your Congressional Representatives.