A JSON polyfill. No longer maintained.

Related tags

Miscellaneous json3
Overview

🚨 Unmaintained 🚨

JSON 3 is **deprecated** and **no longer maintained**. Please don't use it in new projects, and migrate existing projects to use the native `JSON.parse` and `JSON.stringify` instead.

Thanks to everyone who contributed patches or found it useful! ❤️

JSON 3

No Maintenance Intended

JSON 3 was a JSON polyfill for older JavaScript platforms.

About

JSON is a language-independent data interchange format based on a loose subset of the JavaScript grammar. Originally popularized by Douglas Crockford, the format was standardized in the fifth edition of the ECMAScript specification. The 5.1 edition, ratified in June 2011, incorporates several modifications to the grammar pertaining to the serialization of dates.

JSON 3 exposes two functions: stringify() for serializing a JavaScript value to JSON, and parse() for producing a JavaScript value from a JSON source string. The JSON 3 parser uses recursive descent instead of eval and regular expressions, which makes it slower on older platforms compared to JSON 2. The functions behave exactly as described in the ECMAScript spec, except for the date serialization discrepancy noted below.

The project is hosted on GitHub, along with the unit tests. It is part of the BestieJS family, a collection of best-in-class JavaScript libraries that promote cross-platform support, specification precedents, unit testing, and plenty of documentation.

Date Serialization

JSON 3 deviates from the specification in one important way: it does not define Date#toISOString() or Date#toJSON(). This preserves CommonJS compatibility and avoids polluting native prototypes. Instead, date serialization is performed internally by the stringify() implementation: if a date object does not define a custom toJSON() method, it is serialized as a simplified ISO 8601 date-time string.

Several native Date#toJSON() implementations produce date time strings that do not conform to the grammar outlined in the spec. In these environments, JSON 3 will override the native stringify() implementation. There is an issue on file to make these tests less strict.

Portions of the date serialization code are adapted from the date-shim project.

Usage

Web Browsers

<script src="//cdnjs.cloudflare.com/ajax/libs/json3/3.3.2/json3.min.js"></script>
<script>
  JSON.stringify({"Hello": 123});
  // => '{"Hello":123}'
  JSON.parse("[[1, 2, 3], 1, 2, 3, 4]", function (key, value) {
    if (typeof value == "number") {
      value = value % 2 ? "Odd" : "Even";
    }
    return value;
  });
  // => [["Odd", "Even", "Odd"], "Odd", "Even", "Odd", "Even"]
</script>

When used in a web browser, JSON 3 exposes an additional JSON3 object containing the noConflict() and runInContext() functions, as well as aliases to the stringify() and parse() functions.

noConflict and runInContext

  • JSON3.noConflict() restores the original value of the global JSON object and returns a reference to the JSON3 object.
  • JSON3.runInContext([context, exports]) initializes JSON 3 using the given context object (e.g., window, global, etc.), or the global object if omitted. If an exports object is specified, the stringify(), parse(), and runInContext() functions will be attached to it instead of a new object.

Asynchronous Module Loaders

JSON 3 is defined as an anonymous module for compatibility with RequireJS, curl.js, and other asynchronous module loaders.

<script src="//cdnjs.cloudflare.com/ajax/libs/require.js/2.1.10/require.js"></script>
<script>
  require({
    "paths": {
      "json3": "./path/to/json3"
    }
  }, ["json3"], function (JSON) {
    JSON.parse("[1, 2, 3]");
    // => [1, 2, 3]
  });
</script>

To avoid issues with third-party scripts, JSON 3 is exported to the global scope even when used with a module loader. If this behavior is undesired, JSON3.noConflict() can be used to restore the global JSON object to its original value.

Note: If you intend to use JSON3 alongside another module, please do not simply concatenate these modules together, as that would cause multiple define calls in one script, resulting in errors in AMD loaders. The r.js build optimizer can be used instead if you need a single compressed file for production.

CommonJS Environments

var JSON3 = require("./path/to/json3");
JSON3.parse("[1, 2, 3]");
// => [1, 2, 3]

JavaScript Engines

load("path/to/json3.js");
JSON.stringify({"Hello": 123, "Good-bye": 456}, ["Hello"], "\t");
// => '{\n\t"Hello": 123\n}'

Compatibility

JSON 3 has been tested with the following web browsers, CommonJS environments, and JavaScript engines.

Web Browsers

CommonJS Environments

JavaScript Engines

  • Mozilla Rhino 1.7R3 and higher
  • WebKit JSC
  • Google V8

Known Incompatibilities

  • Attempting to serialize the arguments object may produce inconsistent results across environments due to specification version differences. As a workaround, please convert the arguments object to an array first: JSON.stringify([].slice.call(arguments, 0)).

Required Native Methods

JSON 3 assumes that the following methods exist and function as described in the ECMAScript specification:

  • The Number, String, Array, Object, Date, SyntaxError, and TypeError constructors.
  • String.fromCharCode
  • Object#toString
  • Object#hasOwnProperty
  • Function#call
  • Math.floor
  • Number#toString
  • Date#valueOf
  • String.prototype: indexOf, charCodeAt, charAt, slice, replace.
  • Array.prototype: push, pop, join.
Comments
  • Sauce Labs Automated Testing

    Sauce Labs Automated Testing

    Travis CI has already been integrated into JSON3, so I think we can start to implement automated browser testing with Sauce Labs. Lo-Dash has been doing this for some time already, with great results. The only problem with implementing this is that Spec, the test suite we use, is not natively supported, meaning we have to use wd (Selenium/WebDriver library) to access the test results ourselves.

    enhancement 
    opened by bnjmnt4n 16
  • Fix the export in CommonJS environments

    Fix the export in CommonJS environments

    Summary: If the current module is used in a mixed environment, loaded as part of a CommonJS style module, but where the scopechain contains an AMD style 'defined' function, this function would wrongfully use this to define itself instead of exporting using the module/exports variables.

    This diff changes the order of the tests so that it prefers exporting to the module object, then the exports object and finally using define.

    Test Plan: Ran the test suite, and loaded the module inside a local CommonJS environment running in a page also hosting an AMD style loader.

    Reviewers: kitcambridge

    bug enhancement discuss 
    opened by oyvindkinsey 15
  • Native stringify is not being used (at all!) in Firefox due to a (Fx) bug in date serialization

    Native stringify is not being used (at all!) in Firefox due to a (Fx) bug in date serialization

    Due to Firefox bug 730831, Firefox is currently causing the date test to fail and, therefore, always triggering the script-based stringify instead of the native implementation.

    Although this was already triaged to be a Firefox issue, this was created in order to:

    • Act as a reminder, while the Firefox bug is fixed
    // Firefox misses the positive sign - see http://bugzil.la/730831
    
    • Maybe consider creating or providing a workaround to allow Firefox to use its native stringify instead of the script-based emulation
      • when date parsing is not being used or dates are within reasonable timespans, users are currently getting a performance hit without a (good) reason
    • Allow to cross-link both issues so that anyone interested can easily keep up
    bug 
    opened by HelderMagalhaes 14
  • JSON.stringify doesn't work on IDispatch wrappers in JScript

    JSON.stringify doesn't work on IDispatch wrappers in JScript

    If I get an object in Internet Explorer's JScript engine from e.g. an add-on written in C++, I don't get a native JavaScript object. Instead, I get a wrapper that uses Microsoft's IDispatch interface to duplicate the behavior of a native JS object. For example, the hasOwnProperty method will use some IDispatch method (maybe GetIDsOfNames?) to return the correct value.

    In your library, you cache the value of Object.prototype.hasOwnProperty in a variable called isProperty that is reused for all the objects that are passed into the stringify() method. As a result, an object received via IDispatch will use the wrong method (i.e. the default hasOwnProperty instead of the special IDispatch hasOwnProperty). This causes the library to think that it should serialize the object's "constructor" property since isProperty.call(object, "constructor") erroneously returns true. The end result is a type error since it thinks the object has a cyclic structure.

    The right solution might be to check in forEach whether the object is an IDispatch wrapper and always use its hasOwnProperty method if it is. I'm not sure how to determine this, but if this sounds like a viable approach to you, I can have a look around and propose a patch.

    bug 
    opened by matthewgertner 11
  • Opera Testsuite Failures

    Opera Testsuite Failures

    I don't know how correct it is, but Opera has a comprehensive JSON test suite. I used it a few years ago to pinpoint IE8's JSON bugs. When I ran JSON3 against the Opera tests, there were 3 failures.

    The Opera tests claim that JSON.stringify(Math, ["PI"]); should equal {"PI":3.141592653589793} which it does in Firefox 11 Windows. JSON3 returns {}. The other 2 failures were related to stringify-ing arguments which may be open to interpretation as far as the spec goes. Also note that those Opera tests show Firefox has some failures that JSON3 does not; JSON3 Rocks!

    Testsuite URL http://testsuites.opera.com/JSON/runner.htm

    Failures: JSON.stringify() whitelist includes dontEnum properties http://testsuites.opera.com/JSON/correctness/scripts/045.js

    JSON.stringify() and the arguments array http://testsuites.opera.com/JSON/integration/scripts/005.js

    JSON.stringify() and the arguments array - with replacer whitelist http://testsuites.opera.com/JSON/integration/scripts/006.js

    opened by kensnyder 11
  • Use `devDependencies` instead of `vendor`

    Use `devDependencies` instead of `vendor`

    @jdalton recently did this for the other @bestiejs projects, so I was wondering if this could be done for JSON3 as well. Also, this would help to reduce the size of downloads from GitHub, as well as git.

    enhancement 
    opened by bnjmnt4n 6
  • Remove Prototype <= 1.6.1 Support

    Remove Prototype <= 1.6.1 Support

    Prototype <= 1.6.1 support was added quite some time ago, in #8, back when many people were still using outdated versions of Prototype. However, the current Prototype version is 1.7.2 (released this year), and the toJSON bug was fixed in 1.7 (released in 2010).

    However, if we intend to use a replacer function to serialise Dates (as in #65), it might be difficult to ensure that the toJSON property of Strings, Numbers, Arrays and Dates are not called. Thus, I would recommend we remove support for Prototype <= 1.6.1.

    @kitcambridge what do you think?

    enhancement 
    opened by bnjmnt4n 6
  • JSON3 uses a lot of memory in Windows Mobile

    JSON3 uses a lot of memory in Windows Mobile

    Hi!

    I am developing a Windows Mobile 6.5 application (not windows phone, windows mobile), and i use a Webview and a lot of JSON object. I had used json2 but i had quite problems with this one.

    I found this amazing library which resolves all the problems that i had with json2.

    However, this library wastes a lot of memory so in five or six minutes my app haven't memory and throws OutOfMemory. json2 doesn't use so much memory so....is there any reason for this??

    Thanks for your answer!

    PD: Sorry for my bad english.

    bug wontfix 
    opened by ssppgit 6
  • Prototype <= 1.6.1 Support

    Prototype <= 1.6.1 Support

    So...here's the story behind JSON 3 not supporting Prototype <= 1.6.1.

    According to the spec entry for stringify, the toJSON method is used to obtain an alternative object for serialization. For example, Backbone's Model#toJSON returns a plain object containing the model's attributes, which is then serialized using the algorithm defined in the spec. For this behavior to make sense, toJSON should return a string, number, Boolean, array literal, or object literal—the only objects for which the serialization routine is explicitly defined.

    Unfortunately, older versions of Prototype dictate that the toJSON method should return a pre-serialized JSON string. To make matters worse, it also defines toJSON methods on strings, dates, numbers, and arrays (but not booleans)—which means that stringify will call them to obtain a replacement value (a pre-serialized string), and then serialize that value. The result will always be a string literal, rather than a proper JSON structure.

    This behavior is actually consistent with the spec, and using the native implementation will yield identical results. We can confirm this by running the following snippet in a browser that supports native JSON, and without JSON 3 loaded:

    (function() {
      var script = document.createElement("script");
      script.src = "http://prototypejs.org/assets/2009/8/31/prototype.js";
      script.onload = function () {
        // This should be `true`.
        alert(JSON.stringify([1, 2, 3]) == "\"[1, 2, 3]\"");
      };
      document.body.appendChild(script);
    }());
    

    The spec doesn't account for a library that completely redefines how toJSON works, and catering to these versions of Prototype would require breaking compatibility with the spec. The objective of JSON 3 is twofold: provide a spec-complaint polyfill for older browsers, and fix bugs in the native JSON implementations of newer ones. I'm afraid that fixing a buggy, dated library (1.6.1 was released in September 2009; 1.7, which corrects the issues, was released in November 2010) would fall outside the scope of this project.

    A Note on Object.toJSON: The Object.toJSON method provided by Prototype is not an appropriate fallback for JSON.stringify—it doesn't support the filter or whitespace arguments, and will recurse indefinitely when attempting to serialize cyclic structures. Additionally, Prototype's date serialization is broken (it doesn't support extended years or milliseconds, for example), and doesn't work around the bugs present in Opera >= 10.53.

    The only viable option that I can see is to monkey-patch Prototype. There are two significant problems with this approach as well. First, it would involve increasing the size and complexity of the source for a very specific audience. Secondly, even if all of Prototype's buggy methods could be monkey-patched, nothing can be done about third-party code. Remember that Prototype redefines the behavior of toJSON—which means that third-party code that relies on this behavior will break if the library is patched. It's a less than stellar solution.

    I'm certainly open to discussing this, but let's keep in mind that any solution we come up with is likely to be an egregious hack. For that reason, I'd like to tread cautiously before implementing any kind of a patch (@tobie, @savetheclocktower—if you have the time and inclination, I'd love to hear any thoughts that you may have about this).

    bug 
    opened by ghost 6
  • Not working in >IE8

    Not working in >IE8

    I have tried both JSON2 and JSON3, and I can't get it to work. Below is my JSON function, can anyone please tell me what is wrong?

    jQuery(document).ready(function() { (function ($) { $('select[name="post_type"]').change(function (event) { $("#location-dropdown").prop("disabled", true); $('select[name="location"]').html(""); $.post("", { action: 'wpse158929_get_terms_for_cpt', post_type: $(this).val(), taxonomy: , current_selected: $('select[name="location"]').val(), nonce: }, function( response ) { if ( response && !response.error ) { $('select[name="location"]').html(response.html); $("#location-dropdown").prop("disabled", false); } }, 'json' ); }); // Remove if you don't want to call change immediately. $('select[name="post_type"]').change(); })(jQuery); });

    question 
    opened by guit4eva 5
  • New release for Bower

    New release for Bower

    It looks like Bower package was released before ignore option was added to bower.json config and so the current json3 Bower package takes a whopping 6MB.

    Bower doesn't have any kind of lock/shrinkwrap mechanism, so some people might want to add all packages to the repo to avoid surprises when deploying to ci/production servers.

    New release should probably solve this problem.

    opened by szimek 5
  • Looking for new maintainers or deprecating

    Looking for new maintainers or deprecating

    Hello GitHub stargazers,

    I think it's been clear for a while that I've abandoned JSON 3. To the folks watching and using this project, I'm very sorry for letting PRs slide, and for my inattention to new issues. It's upsetting to see contributions ignored, and you have every right to feel frustrated. Procrastinating, instead of asking for help and looking for new maintainers, was not a constructive way to sunset the project. I will do better in the future.

    TL;DR: If you'd like to take over JSON 3, please reply to this issue. I'll leave it open until 17 March 2017. After that, I'll update the readme, description, and package managers to indicate the project is obsolete and unmaintained. I won't delete or unpublish it, but you should definitely think about using JSON 2, or removing the polyfill entirely. In the meantime, I'll go through and merge or close outstanding PRs and issues.

    So, what's the state of the project? Short answer: old and busted. Longer answer:

    • It's slow. eval isn't a speed demon, but walking large strings character-by-character in a big loop, then recursing into objects and arrays, will lock up old browsers. We've had several issues like that. The included "benchmark" is a 168-byte string, plus some longer strings in the jsPerf that run on modern browsers. The claim that this design "provides security and performance benefits in obsolete and mobile environments" is blatantly wrong, and I shouldn't have made it in the first place. If you pick and choose what you're looking for, and don't test on platforms that need this most, of course it's going to perform well!

    • It's big. 3.5k is a lot, especially on mobile. For comparison, a core build of Lodash is 4k, and it's packed with useful functions. This, OTOH, is a library-sized polyfill that does something your browser can already do, and that most don't even need. All browsers have had fully compliant implementations (or mostly compliant, with weird edge cases that don't matter) for years. For example, there's a feature test that checks if six-digit years are stringified correctly. How many apps need to work with dates 275k years into the past or future?

    • It's old. The description "a modern JSON implementation" is about 5 years out of date. Our feature tests check for bugs in IE 7, Firefox 3, and Safari 5, which are 10, 8, and 7 years old. The modern web would be unusable on one of these browsers today. It's fun to say we can technically support hipster browsers that run on Windows 2000, but that means nothing if you can't actually use the web. A JSON polyfill won't change that.

    • It's overly clever. The lex function is a giant loop that sets and reads from global state. There are several one-liners and empty loop bodies that I thought "clever" 5 years ago, but that just make the code unreadable, and make linters complain. This isn't JS1k or an Obfuscated C/Perl code contest. Clever code is for fun and minifiers, not boring libraries.

    • It's monolithic. The library is wrapped in a giant IIFE, with conditional exports, feature tests, and shared helpers strewn about. I started working on a webpack-based build system, and had vague ideas about pluggable parsers and conditional builds. But that means introducing more bloat into an already big library, and I'm not sure it's worth it. Browsers released since 5 years ago haven't needed JSON 3, I don't think custom builds are the answer.

    There's one more reason, and it's that I haven't had much time to fix outstanding issues. Maintaining a crufty project like this takes discipline, and it's easy to get distracted by other things.

    So...if you've read through this Saturday afternoon rant, thank you. If you've contributed a patch to JSON 3, or found it useful, thank you. A big thank you especially to @demoneaux, who optimized the parser as much as he could, removed support for ancient environments, cleaned up the code, and set up tests.

    If you'd like to maintain it, I'll take the time to help you get set up, and go through the backlog of issues. If not, the project will still be here, but with a warning that you probably shouldn't use it. I picked 17 March 2017 arbitrarily, so that I can follow through, instead of letting this sit for two more years.

    help wanted 
    opened by ghost 2
  • JSON.stringify is not a function

    JSON.stringify is not a function

    Hello,

    I am having a strange issue with JSON.stringify when using browserify. Most times it works as expected, while I get an Uncaught TypeError: JSON.stringify is not a function error on certain pages of a website.

    I suspect that window.JSON is somehow modified by another script running in the same page, but I thought that using require and browserify I could scope my own JSON object to use locally hopefully not affecting other definitions, or other scripts affecting mine.

    For more context, here's how I use it:

    var JSON = require('json3');
    
    var MyObject = module.exports = function() {}
    
    MyObject.prototype.doSomething() {
       // JSON.stringify({...})
    }
    

    Should I use the runInContect or noConflict helpers that were released recently? Have I missed something entirely?

    Your help is much appreciated 😃

    opened by alexkappa 2
  • json3 dosn't run in VM

    json3 dosn't run in VM

    Hay, i have a little problem.

    I cant use json3 (socket.io, btw. socket.io-client) inside a node js VM. When i run it i become this error: "TypeError: Cannot read property 'prototype' of undefined"

    /home/marc/NetBeansProjects/Project/node_modules/socket.io-client/node_modules/json3/lib/json3.js:50 var objectProto = Object.prototype, ^ TypeError: Cannot read property 'prototype' of undefined at runInContext (/home/marc/NetBeansProjects/Project/node_modules/socket.io-client/node_modules/json3/lib/json3.js:50:29)

    As VM i use the module "sandboxed-module" (https://github.com/felixge/node-sandboxed-module)

    See other issue on: https://github.com/socketio/socket.io/issues/2381#issuecomment-172353479

    opened by mStirner 5
  • json.stringify undefined in IE7

    json.stringify undefined in IE7

    Hello there,

    Today at Browserling I had to debug an issue for a customer in IE7. He was using socket.io (latest v1.3.7), that uses json3.

    I found out that in IE7 json.stringify is undefined, however json.JSON.stringify is defined.

    Here's a screenshot from debugger attached to IE7 that shows the problem (it's in socket.io-client.js):

    image

    I'm not sure if it's json3 issue, or socket.io-client.js issue, but as a workaround I'm simply using json.JSON.stringify in that place. I thought I'd let you know.

    P. Krumins

    opened by pkrumins 2
  • Build issue, strict mode required for conformance to in-house guidelines

    Build issue, strict mode required for conformance to in-house guidelines

    Would it be possible to add 'use strict'; to json3? Does the code conform to the requirements of using strict mode?

    Part of our in-house build script uses JSLint to check Javascript modules. One of the requirements is that all modules must be processed in strict mode. Also as part of open-source agreement we are not permitted to modify the source directly.

    Best regards,

    Mark

    opened by MarkAddison 0
EventSource polyfill

EventSource polyfill - https://html.spec.whatwg.org/multipage/server-sent-events.html#server-sent-events Installing: You can get the code from npm or

Viktor 1.9k Jan 9, 2023
JSON Diff Kit - A better JSON differ & viewer

A better JSON differ & viewer, support LCS diff for arrays and recognise some changes as modification apart from simple remove+add.

Rex Zeng 38 Dec 18, 2022
Generate HTML redirections from json file

Generate HTML redirections from json file

Andrew Luca 3 Jan 6, 2022
🧠 100'den fazla gereksiz bilgi ile oluşturulmuş bir JSON API.

?? Gereksiz Bilgiler API 100'den fazla gereksiz bilgi ile oluşturulmuş bir JSON API.

Orhan Emre Dikicigil 3 Sep 23, 2022
Tooling to automate converting .xlsx localisation to in-game compatible .json files for Vampire Survivors

vampire-survivors-localisation This tooling is used to automate converting .xlsx localisation to in-game compatible .json files for the game Vampire S

null 17 Dec 8, 2022
Defines the communication layer between mobile native(iOS/Android) and webview using JSON Schema and automatically generates SDK code

Defines the communication layer between mobile native(iOS/Android) and webview using JSON Schema and automatically generates SDK code.

당근마켓 31 Dec 8, 2022
⚠️ [Deprecated] No longer maintained, please use https://github.com/fengyuanchen/jquery-cropper

Cropper A simple jQuery image cropping plugin. As of v4.0.0, the core code of Cropper is replaced with Cropper.js. Demo Cropper.js - JavaScript image

Fengyuan Chen 7.8k Dec 27, 2022
No longer maintained, superseded by JS Cookie:

IMPORTANT! This project was moved to https://github.com/js-cookie/js-cookie, check the discussion. New issues should be opened at https://github.com/j

Klaus Hartl 8.6k Jan 5, 2023
CasperJS is no longer actively maintained. Navigation scripting and testing utility for PhantomJS and SlimerJS

CasperJS Important note: the master branch hosts the development version of CasperJS, which is now pretty stable and should be the right version to us

CasperJS 7.3k Dec 25, 2022
⚠️ [Deprecated] No longer maintained, please use https://github.com/fengyuanchen/jquery-viewer

Viewer A simple jQuery image viewing plugin. As of v1.0.0, the core code of Viewer is replaced with Viewer.js. Demo Viewer.js - JavaScript image viewe

Fengyuan Chen 1k Dec 19, 2022
No longer actively maintained.

Vide No longer actively maintained. I am not interested to maintain jQuery plugins anymore. If you have some fixes, feel free to make PR. Easy as hell

Ilya Caulfield 3.3k Dec 20, 2022
No longer actively maintained.

Remodal No longer actively maintained. I am not interested to maintain jQuery plugins anymore. If you have some fixes, feel free to make PR. Responsiv

Ilya Caulfield 2.8k Dec 11, 2022
The fastest JSON schema Validator. Supports JSON Schema draft-04/06/07/2019-09/2020-12 and JSON Type Definition (RFC8927)

Ajv JSON schema validator The fastest JSON validator for Node.js and browser. Supports JSON Schema draft-06/07/2019-09/2020-12 (draft-04 is supported

Ajv JSON schema validator 12k Jan 4, 2023
JCS (JSON Canonicalization Scheme), JSON digests, and JSON Merkle hashes

JSON Hash This package contains the following JSON utilties for Deno: digest.ts provides cryptographic hash digests of JSON trees. It guarantee that d

Hong Minhee (洪 民憙) 13 Sep 2, 2022
Package fetcher is a bot messenger which gather npm packages by uploading either a json file (package.json) or a picture representing package.json. To continue...

package-fetcher Ce projet contient un boilerplate pour un bot messenger et l'executable Windows ngrok qui va permettre de créer un tunnel https pour c

AILI Fida Aliotti Christino 2 Mar 29, 2022
JSON Hero is an open-source, beautiful JSON explorer for the web that lets you browse, search and navigate your JSON files at speed. 🚀

JSON Hero makes reading and understand JSON files easy by giving you a clean and beautiful UI packed with extra features.

JSON Hero 7.2k Jan 9, 2023
Marquee is a VS Code extension designed to naturally integrate with your development flow, so that you will no longer lose track of your thoughts while you're coding

Marquee Stay organized with minimal context switching, all inside your Visual Studio Code. Marquee is a VS Code extension designed to naturally integr

stateful 60 Dec 13, 2022
"Longer in Twitter" est une extension Chrome affichant les TwitLonger directement dans un tweet.

Longer in Twitter "Longer in Twitter" est une extension Chrome affichant les TwitLonger directement dans un tweet. Installation Longer in Twitter ne f

Johan le stickman 4 Sep 22, 2022
⚠️ This project is not maintained anymore! Please go to https://github.com/visjs

vis.js (deprecated!) ❗ This project is not maintained anymore! (See Issue #4259 for details) We welcome you to use the libraries from the visjs commun

null 7.9k Dec 27, 2022
A responsive image polyfill for , srcset, sizes, and more

Picturefill A responsive image polyfill. Authors: See Authors.txt License: MIT Picturefill has three versions: Version 1 mimics the Picture element pa

Scott Jehl 10k Dec 31, 2022