uBlock/.jshintrc

{
	"browser": true,
	"devel": true,
	"eqeqeq": true,
	"esversion": 6,
	"globals": {
		"browser": false,    // global variable in Firefox, Edge
		"chrome": false,     // global variable in Chromium, Chrome, Opera
		"Components": false, // global variable in Firefox
		"log": false,
		"safari": false,
		"self": false,
		"vAPI": false,
		"µBlock": false
	},
	"laxbreak": true,
	"newcap": false,
	"nonew": false,
	"strict": "global",
	"sub": true,
	"undef": true,
	"unused": true,
	"validthis": true
}
Add .jshintrc, and use the "use strict" directive .jshintrc's otion-set is a personal choice, merely a suggestion. Beside that, it includes some common globals for specific browsers, so there's no need to set the globals in every .js file. In order to force strict coding, "use strict" directive was added into every .js file. 2014-10-19 13:11:27 +02:00			`{`
			`"browser": true,`
			`"devel": true,`
code review: convert static filtering's tokenizer to a global utility 2015-12-29 17:34:41 +01:00			`"eqeqeq": true,`
Use `esversion` instead of deprecated `esnext` 2019-02-08 15:45:25 +01:00			`"esversion": 6,`
code review: convert static filtering's tokenizer to a global utility 2015-12-29 17:34:41 +01:00			`"globals": {`
fix #2925 2017-08-30 00:32:00 +02:00			`"browser": false, // global variable in Firefox, Edge`
			`"chrome": false, // global variable in Chromium, Chrome, Opera`
code review: convert static filtering's tokenizer to a global utility 2015-12-29 17:34:41 +01:00			`"Components": false, // global variable in Firefox`
Refactor selfie generation into a more flexible persistence mechanism The motivation is to address the higher peak memory usage at launch time with 3rd-gen HNTrie when a selfie was present. The selfie generation prior to this change was to collect all filtering data into a single data structure, and then to serialize that whole structure at once into storage (using JSON.stringify). However, HNTrie serialization requires that a large UintArray32 be converted into a plain JS array, which itslef would be indirectly converted into a JSON string. This was the main reason why peak memory usage would be higher at launch from selfie, since the JSON string would need to be wholly unserialized into JS objects, which themselves would need to be converted into more specialized data structures (like that Uint32Array one). The solution to lower peak memory usage at launch is to refactor selfie generation to allow a more piecemeal approach: each filtering component is given the ability to serialize itself rather than to be forced to be embedded in the master selfie. With this approach, the HNTrie buffer can now serialize to its own storage by converting the buffer data directly into a string which can be directly sent to storage. This avoiding expensive intermediate steps such as converting into a JS array and then to a JSON string. As part of the refactoring, there was also opportunistic code upgrade to ES6 and Promise (eventually all of uBO's code will be proper ES6). Additionally, the polyfill to bring getBytesInUse() to Firefox has been revisited to replace the rather expensive previous implementation with an implementation with virtually no overhead. 2019-02-14 19:33:55 +01:00			`"log": false,`
code review: convert static filtering's tokenizer to a global utility 2015-12-29 17:34:41 +01:00			`"safari": false,`
			`"self": false,`
			`"vAPI": false,`
			`"µBlock": false`
			`},`
			`"laxbreak": true,`
			`"newcap": false,`
Add .jshintrc, and use the "use strict" directive .jshintrc's otion-set is a personal choice, merely a suggestion. Beside that, it includes some common globals for specific browsers, so there's no need to set the globals in every .js file. In order to force strict coding, "use strict" directive was added into every .js file. 2014-10-19 13:11:27 +02:00			`"nonew": false,`
code review: convert static filtering's tokenizer to a global utility 2015-12-29 17:34:41 +01:00			`"strict": "global",`
Add .jshintrc, and use the "use strict" directive .jshintrc's otion-set is a personal choice, merely a suggestion. Beside that, it includes some common globals for specific browsers, so there's no need to set the globals in every .js file. In order to force strict coding, "use strict" directive was added into every .js file. 2014-10-19 13:11:27 +02:00			`"sub": true,`
code review: convert static filtering's tokenizer to a global utility 2015-12-29 17:34:41 +01:00			`"undef": true,`
			`"unused": true,`
adjust jshint behavior 2017-12-05 14:38:50 +01:00			`"validthis": true`
#608: this fixes a bunch of strictness-related warnings 2015-08-18 17:44:24 +02:00			`}`