Skip to content

v4.0.0

@balupton balupton tagged this 20 Oct 11:08
- `parseCSString` no longer creates the `sandbox` variable if it was
missing, the responsibility of such things should be, and now is,
handled via the eval function of coffeescript which is what that method
uses
	- This is a major breaking change as parsing coffeescript files
	will now by default run still in a virtual machine but now in
	the global context rather than their own context
		 	- If you are parsing untrusted coffeescript
			files, you should now setup the `sandbox` option
			yourself with the appropriate values
					- If you are parsing trusted
					coffeescript files, or not
					parsing coffeescript files (e.g.
					only CSON files), then this
					change won't impact you
						- This change is done
						such that the result
						object from
						`parseCSString` passes
						`result.__proto__ ===
						Object.prototype` which
						before it did not as the
						different context caused
						the prototype to point
						to a different contexts
						`Object` causing the
						assertion to fail
						- Updated dependencies
						- Updated internal
						packing conventions
Assets 2
Loading