Releases: NativeScript/ios-jsc
Releases · NativeScript/ios-jsc
NativeScript for iOS version 1.3.0
What's New
- Embed metadata in binary so it can be stripped by App Thinning (#275)
- Swift modules use mangled name which is different than the klassName so get the name from the metadata (#274)
- Require with tilde (~) should resolve to the app folder (#254)
- Pause the debugger on startup with --debug-brk (#245)
- Web Inspector Page Agent (#240)
- Two-way marshaling between NSData and ArrayBuffer (#235)
- JavaScript functions, when passed to Objective-C as blocks, will now round-trip back to JavaScript, as the initial function object. (#234)
- Create a global require function (#84)
Bug Fixes
- Error when file ends with a commented line (#288)
- NativeScript::SymbolLoader incorrectly caches framework bundles (#273)
- Better handling of package.json main configuration (#270)
- Expose a conversion between ArrayBuffers and NSData (#231)
- Require doesn't look for index.js in main folder (#112)
- Delete the module cache when a module throws an exception (#20)
- NSDecimalNumber marshalling (#14)
- Explicitly set the metadata generator's OS X deployment target (#285)
- -[TNSValueWrapper value] can return null (#262)
NativeScript for iOS version 1.2.2
NativeScript for iOS version 1.2.1
NativeScript for iOS version 1.2.0
What's New
- Implement and consume NSFastEnumeration (#222)
- Memory management of class clusters (#214)
- Update to the latest JavaScriptCore (#211)
- Add application that uses the updated webkit webview to show web inspector frontend (#201)
- Transform (NSError **) parameters to JavaScript error throw (#186)
- CMake the JSC: Performance and memory diffs (#185)
- iOS 9 Support: Metadata for Objective-C Generics (#177)
- WebInspector: Enable WebInspector Performance Profiler (#164)
- Optimize require of JavaScript modules (#139)
Bug Fixes
NativeScript for iOS version 1.1.0
- NativeScript for iOS is now built using CMake
- The runtime is now distributed as a static library and a Cocoa Framework
- The NativeScript CLI iOS template project now strips non-device architectures from embedded frameworks
- API Metadata now includes information about Clang modules
- You can now require paths with .js extension
- NativeScript apps for iOS no longer ship with a WebSocket server for debugging, but rely on a plain TCP socket instead
- Fixed issue where invoking an Objective-C class cluster as a JavaScript constructor with
new
would cause memory leaks - Fixed issue where an inspector frontend connecting to the same app multiple times in a single session would not display sources
- Accessing JavaScript from multiple threads is properly synchronized
NativeScript for iOS version 0.10.0
We've just passed the 0.10.0 milestone and here are some exciting changes that happend in the ios runtime:
Runtime
Issues | Description |
---|---|
#4 | We will try to freeze the application on crash if there is a debugger attached so the debugger can be used to examine the errors. |
#4 | When Objective-C exception is thrown from code called from JavaScript, it will be wrapped in JavaScript Error and reported to the debugger. |
#23 | We have fixed the “tagged pointers“ bug on iPhone 5s with iOS7.0. |
We have dramatically reduced the “tns-ios” package size by stripping the debug symbols from the NativeScript.framework. | |
We have fixed the project template to support properly the app-id provided from the CLI. | |
#48, #43 | We’ve cleaned the package.tgz from some xcodebuild logs and the Chrome version of the inspector. |
#31, #34, #16 | Made submodules public, fixed builds |
#40 | tns_modules are now expected in the app folder. We are backward compatible but will remove the compatibility in future. |
#65 | We have updated the project template to use larger resolution |
#39 | Promise reactions have too low a priority on the runloop |
JavaScript API
Issues | Description |
---|---|
JavaScript Date is implicitly converted to NSDate and vice versa. | |
JSON object and JS Map, when passed to native, are wrapped in NSDictionary. NSDictionaries do not behave as JSON objects when returned from native. |