one 1.4.0 → 1.4.2

package/LICENSE

@@ -0,0 +1,37 @@
+BSD-3-Clause License
+
+Copyright (c) 2022 Evan Bacon
+
+Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
+
+3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+---
+
+The MIT License (MIT)
+
+Copyright (c) 2015-present 650 Industries, Inc. (aka Expo)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,75 +1,3 @@
-OneJS is a command-line utility for converting CommonJS packages to single, stand-alone JavaScript
-files that can be run on web browsers.
+One is a new React Framework that makes Vite serve both native and web.
 
-# Motivation
-* **Reusability** OneJS lets developers code JavaScript for one platform and run everywhere, without requiring any additional effort.
-* **Elegant Modularization** Modules and packages specs of CommonJS are what web apps exactly needs: a very well designed way to structure JavaScript code.
-* **NPM** OneJS moves the revolution of NPM one step forward and makes it available for client-side projects!
-* **No Spaghetti Code** No awkward headers, no framework-specific definitions.
-* **Reliable code generation** OneJS doesn't change your source code. It generates a container that emulates a simple NodeJS environment.
-* **Unobtrusive Code** OneJS puts all the content into an isolated JS object.
-
-![](http://oi41.tinypic.com/aw2us3.jpg)
-
-### Examples
-* See the example project included in this repository
-* MultiplayerChess.com ([Source Code](https://github.com/azer/multiplayerchess.com/tree/master/frontend) - [Output](http://multiplayerchess.com/mpc.js) )
-* [boxcars](https://github.com/azer/boxcars)
-
-# Install
-```bash
-$ npm install one
-```
-
-# First Steps
-
-## Creating the Bundle Script
-
-OneJS walks the modules and dependencies defined by package.json files. To create your bundle, just go a project directory and type `onejs build` command:
-
-```
-$ onejs build package.json bundle.js
-```
-
-## Experimenting the Bundle Script
-
-The output OneJS generates can be used by NodeJS, too. It's the easiest way of making sure if the output works or not. 
-
-```
-> var exampleProject = require('./bundle');
-> exampleProject.main() // calls main module, returns its exports
-> exampleProject.require('./b') // each package object has a require method available for external calls
-```
-
-In the case what you need is to try it in web browsers, onejs has a "server" option that'll publish the source code at `localhost:1338` let you debug the output with Firebug Lite easily;
-
-```
-$ ../bin/onejs server example-project/package.json
-```
-
-## Using the NodeJS Core Library
-
-Many modules of the core NodeJS library is able to be used by web projects, as well. OneJS has an 'install' command that converts demanded remote NodeJS module to a package on the fly:
-
-```javascript
-> onejs install assert path url
-```
-
-The reference of available modules that you can install: https://github.com/azer/onejs/blob/master/lib/install_dict.js
-
-## Process
-
-OneJS includes a simple emulation of [NodeJS' process](http://nodejs.org/api/process.html). (Pass --noprocess if you don't need it)
-
-```javascript
-> exampleProject.require('dependency'), exampleProject.require('./b');
-> exampleProject.lib.process.stdout.write("Hello World");
-> exampleProject.stdout();
-"Hello World"
-```
-
-# Troubleshooting
-
-* The most common issue of a OneJS output is to lack some dependencies. In that case, make sure that the library is located under `node_modules/` properly.
-* Enabling verbose mode might be helpful: `onejs build package.json --verbose`
-* See the content of `projectName.map` object if it contains the missing dependency
+See: https://onestack.dev

package/devtools/dev.mjs

@@ -0,0 +1,44 @@
+// main dev entry - imports all dev scripts
+// this file is served as /@one/dev.js by the devtools plugin
+
+import { createHotContext } from '/@vite/client'
+import { injectIntoGlobalHook } from '/@react-refresh'
+
+// route HMR
+const routeHot = createHotContext('/__one_route_hmr')
+routeHot.on('one:route-update', (data) => {
+  if (window.__oneRouteCache) {
+    if (data?.file) {
+      window.__oneRouteCache.clearFile(data.file)
+    } else {
+      window.__oneRouteCache.clear()
+    }
+  }
+  window.dispatchEvent(new CustomEvent('one-hmr-update'))
+})
+
+// loader HMR
+const loaderHot = createHotContext('/__one_loader_hmr')
+loaderHot.on('one:loader-data-update', async (data) => {
+  if (data?.routePaths && window.__oneRefetchLoader) {
+    const currentPath = window.location.pathname.replace(/\/$/, '') || '/'
+    for (const routePath of data.routePaths) {
+      if (routePath === currentPath) {
+        try {
+          await window.__oneRefetchLoader(routePath)
+        } catch (err) {
+          console.error('[one] Error refetching loader:', err)
+        }
+      }
+    }
+  }
+})
+
+// react refresh
+injectIntoGlobalHook(window)
+window.$RefreshReg$ = () => {}
+window.$RefreshSig$ = () => (type) => type
+
+// devtools UI
+import './devtools.mjs'
+import './source-inspector.mjs'