12th July, 2023. I'm going to try creating an iOS app called Paranovel, using Expo. My environment for mobile app dev (Xcode, Ruby, etc.) should be in reasonably good shape already as I frequently develop with React Native and NativeScript.
Go to https://docs.expo.dev, and see the Quick Start: npx create-expo-app paranovel
This runs with no problem, then I get this macOS system popup:
Given the following Nix packages (you may be able to install six manually rather than managing it by Nix, but anyway, this was my setup):
pkgs.python310Full
pkgs.python310Packages.six
I would very often run into this situation:
/usr/local/bin/pip: /usr/local/opt/python/bin/python2.7: bad interpreter: No such file or directory
For example, for the NSString.h header:
clang \
-Xclang \
-ast-dump \
-fsyntax-only \
-x objective-c \
-I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Foundation.framework/Headers \
-F/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks \
This focuses on the V8 iOS metadata generator.
https://github.com/NativeScript/ns-v8ios-runtime/tree/main/metadata-generator
NativeScript is a JavaScript runtime that allows you to write an iOS or Android app entirely in TypeScript or JavaScript with no compromises. That is to say, it provides you with the same level of native access that writing the app in Obj-C/Swift (for iOS) or Java/Kotlin (for Android) does. Not just JSON-serialisable data types like NSString, but all data types are supported. To illustrate what it's all about, here's how you would get the battery level using NativeScript (the below snippet is entirely JS code!):
import { isIOS, isAndroid, Application } from "@nativescript/core";
/**
| <script lang="ts"> | |
| import Popover from "./Popover.svelte"; | |
| import InputView from "./InputView.svelte"; | |
| import { onMount } from "svelte"; | |
| import type { InputViewProps } from "./InputInterfaces"; | |
| import { InputParser } from "./InputParser"; | |
| import Loader from "./Loader.svelte"; | |
| export let inputModel: InputViewProps|undefined = void 0; | |
| export const inputParser: InputParser = new InputParser(); |
| import WebKit | |
| import UIKit | |
| class ViewController: UIViewController { | |
| let webView: WKWebView = WKWebView(frame: self.view.frame, configuration: WKWebViewConfiguration()) | |
| override func loadView() { | |
| super.loadView() | |
| self.view = webView |
In this article, we'll learn how NativeScript was adapted into so many different flavours (Angular, Vue, React, Svelte, and more). We'll cover what makes it such a good target for adapting, but also lift the curtain on some of the technical challenges involved in the process. And through the article, you should gain a sense of what's involved in creating a new flavour for NativeScript (or indeed any other host!).
NativeScript's cross-platform UI modules (broadly everything under the ui directory in the @nativescript/core npm package) can be described as a "UI runtime". In other words, a library that allows you to manipulate the user interface for your app while it is running.
I have a brand new M1 MacBook Pro. I have a long list of complaints with homebrew, so I want to try Nix as my package manager instead, along with Home Manager to control my setup on a per-user basis. Once I've set this all up, theoretically, I should be able to reuse the same configuration on any other Macs I own.
A reproducible, declarative package manager.
More info:
In SvelteKit projects, SvelteKit wraps around Vite.
This example is for configuring path aliases, but you get the idea. There's a kit.vite property in svelte.config.js, and you'd configure vite through there.
https://kit.svelte.dev/faq#aliases
Vite's plugins should be API-compatible with Rollup, to my understanding.