Replace @XDN package

Author: tristanlee85

components/utils/useSegment.js

@@ -20,7 +20,7 @@ export default function useSegment() {
 
   useEffect(() => {
     const segmentLoadInterval = setInterval(() => {
-      if (window.analytics) {
+      if (window.analytics && window.analytics.user) {
         const id = query.sgId || window.analytics.user().anonymousId()
         if (query.sgId) {
           window.analytics.alias(id)

constants.js

@@ -1,5 +1,6 @@
 export const PRODUCT_NAME = 'Layer0'
 export const CLI_NAME = 'l0'
+export const PACKAGE_NAME = '@l0'
 
 export const DOMAIN = 'layer0.co'
 export const APP_DOMAIN = `app.${DOMAIN}`

guides/angular.md

@@ -54,7 +54,7 @@ To prepare your Angular application for deployment on {{ PRODUCT_NAME }}:
 #### 1. Install {{ PRODUCT_NAME }} CLI globally:
 
 ```bash
-npm install -g @xdn/cli
+npm install -g {{ PACKAGE_NAME }}/cli
 ```
 
 #### 2. Run the following in the root folder of your project. This will configure your project for {{ PRODUCT_NAME }}.
@@ -65,9 +65,9 @@ xdn init
 
 This will automatically add all of the required dependencies and files to your project. These include:
 
-- The `@xdn/core` package
-- The `@xdn/angular` package
-- The `@xdn/cli` package
+- The `{{ PACKAGE_NAME }}/core` package
+- The `{{ PACKAGE_NAME }}/angular` package
+- The `{{ PACKAGE_NAME }}/cli` package
 - `xdn.config.js`- Contains various configuration options for {{ PRODUCT_NAME }}.
 - `routes.js` - A default routes file that sends all requests to the Angular Universal server. Update this file to add caching or proxy some URLs to a different origin.
 
@@ -83,8 +83,8 @@ The default `routes.js` file created by `xdn init` sends all requests to Angular
 // This file was automatically added by xdn deploy.
 // You should commit this file to source control.
 
-const { Router } = require('@xdn/core/router')
-import { angularRoutes } from '@xdn/angular'
+const { Router } = require('{{ PACKAGE_NAME }}/core/router')
+import { angularRoutes } from '{{ PACKAGE_NAME }}/angular'
 
 export default new Router().use(angularRoutes)
 ```

guides/caching.md

@@ -15,7 +15,7 @@ Each edge point-of-presence (POP) has its own L1 cache. If a request cannot be f
 To cache a response, use the [cache](/docs/api/core/classes/_router_responsewriter_.responsewriter.html#cache) function in your route's callback:
 
 ```js
-import { CustomCacheKey } from '@xdn/core/router'
+import { CustomCacheKey } from '{{ PACKAGE_NAME }}/core/router'
 
 router.get('/some/path', ({ cache }) => {
   cache({
@@ -73,7 +73,7 @@ It is often useful to customize the cache key, either to improve the cache hit r
 - Increasing the cache hit ratio by excluding query parameters that are not used in the rendering of the content:
 
 ```js
-import { CustomCacheKey } from '@xdn/core/router'
+import { CustomCacheKey } from '{{ PACKAGE_NAME }}/core/router'
 
 router.get('/some/path', ({ cache }) => {
   cache({
@@ -88,7 +88,7 @@ This will remove the given query parameters from the URL before it is used in ca
 - Including other request parameters like cookies:
 
 ```js
-import { CustomCacheKey } from '@xdn/core/router'
+import { CustomCacheKey } from '{{ PACKAGE_NAME }}/core/router'
 
 router.get('/some/path', ({ cache }) => {
   cache({
@@ -103,7 +103,7 @@ This will take the values of `language` and `currency` cookies from `cookie` req
 - Splitting the cache based on device type:
 
 ```js
-import { CustomCacheKey } from '@xdn/core/router'
+import { CustomCacheKey } from '{{ PACKAGE_NAME }}/core/router'
 
 router.get('/some/path', ({ cache }) => {
   cache({

guides/cli.md

@@ -7,13 +7,13 @@ This guide shows you everything you can do with the XDN command line interface.
 To install the XDN CLI run
 
 ```bash
-npm i -g @xdn/cli
+npm i -g {{ PACKAGE_NAME }}/cli
 ```
 
 Or with yarn:
 
 ```bash
-yarn global add @xdn/cli
+yarn global add {{ PACKAGE_NAME }}/cli
 ```
 
 ## Commands
@@ -197,7 +197,7 @@ Production mode is always used whe running downloaded bundles.
 
 ### use
 
-Switches the version of all @xdn/\* packages in your project.
+Switches the version of all {{ PACKAGE_NAME }}/\* packages in your project.
 
 #### Example
 

guides/connectors.md

@@ -1,6 +1,6 @@
 # Connectors
 
-Connector packages help build and run your app within the XDN. When you run `xdn init`, the XDN CLI detects the framework used by your app and installs the corresponding connector package. For example, if you use Next.js, `@xdn/next` will be installed. If no connector package exists for the framework that you use, you can still deploy to the XDN by implementing the connector interface directly in your app.
+Connector packages help build and run your app within the XDN. When you run `xdn init`, the XDN CLI detects the framework used by your app and installs the corresponding connector package. For example, if you use Next.js, `{{ PACKAGE_NAME }}/next` will be installed. If no connector package exists for the framework that you use, you can still deploy to the XDN by implementing the connector interface directly in your app.
 
 ## Writing a connector
 
@@ -24,7 +24,7 @@ Example:
 ```js
 /* istanbul ignore file */
 const { join } = require('path')
-const { DeploymentBuilder } = require('@xdn/core/deploy')
+const { DeploymentBuilder } = require('{{ PACKAGE_NAME }}/core/deploy')
 
 /**
  * Called when the user runs xdn init.
@@ -57,14 +57,14 @@ Additional files can be added beyond the ones listed above. They will be copied
 
 ## dev.js
 
-Called when the user runs `xdn dev`. This entry point is responsible for starting the user's application in development mode. The `@xdn/core` library provides a `createDevServer` function to help with this.
+Called when the user runs `xdn dev`. This entry point is responsible for starting the user's application in development mode. The `{{ PACKAGE_NAME }}/core` library provides a `createDevServer` function to help with this.
 
 _Optional, if not provided, xdn dev will simply start the XDN in local development mode, but will not start a framework application server._
 
 Example:
 
 ```js
-const { createDevServer } = require('@xdn/core/dev')
+const { createDevServer } = require('{{ PACKAGE_NAME }}/core/dev')
 
 module.exports = function() {
   return createDevServer({
@@ -87,15 +87,15 @@ module.exports = function() {
 
 ## build.js
 
-Exports a function that is called when you run `xdn build`. It is responsible for constructing the bundle that is deployed to the XDN cloud. This function typically uses `@xdn/core/deploy/DeploymentBuilder` to stage the exploded bundle in the `.xdn` directory.
+Exports a function that is called when you run `xdn build`. It is responsible for constructing the bundle that is deployed to the XDN cloud. This function typically uses `{{ PACKAGE_NAME }}/core/deploy/DeploymentBuilder` to stage the exploded bundle in the `.xdn` directory.
 
 _Optional, and not needed in most cases. The xdn build command automatically creates a bundle that includes all static assets referenced in your routes file as well as the `prod` entry point mentioned above._
 
 Example:
 
 ```js
-const { DeploymentBuilder } = require('@xdn/core/deploy')
-const FrameworkBuildError = require('@xdn/core/errors/FrameworkBuildError')
+const { DeploymentBuilder } = require('{{ PACKAGE_NAME }}/core/deploy')
+const FrameworkBuildError = require('{{ PACKAGE_NAME }}/core/errors/FrameworkBuildError')
 
 export default async function build({ skipFramework }) {
   const builder = new DeploymentBuilder(appDir)

guides/cookbook.md

@@ -247,7 +247,7 @@ router.get('/products/:id', ({ serveStatic, cache, renderWithApp }) => {
 ```
 
 This hybrid of static and dynamic rendering was first introduced in Next.js as [Incremental Static Generation (ISG)](https://nextjs.org/docs/basic-features/data-fetching#the-fallback-key-required). In Next.js apps, developers enable this behavior by returning `fallback: true` from
-`getStaticPaths()`. The `@xdn/next` package automatically configures the routes for ISG pages to use `onNotFound` and `loadingPage`.
+`getStaticPaths()`. The `{{ PACKAGE_NAME }}/next` package automatically configures the routes for ISG pages to use `onNotFound` and `loadingPage`.
 
 ### Returning a custom 404 page
 

guides/core_web_vitals.md

@@ -27,7 +27,7 @@ Instead of relying solely on Google Search Console, we recommend tracking Core W
 
 ## Installation
 
-In order to start tracking Core Web Vitals on {{ PRODUCT_NAME }}, you need add the `@xdn/rum` client library to your application. There are a number of ways to do this:
+In order to start tracking Core Web Vitals on {{ PRODUCT_NAME }}, you need add the `{{ PACKAGE_NAME }}/rum` client library to your application. There are a number of ways to do this:
 
 ### Script Tag
 
@@ -67,19 +67,19 @@ To add Core Web Vitals tracking via a script tag, add the following to each page
 To install the Core Web Vitals library using npm, run:
 
 ```
-npm install --save @xdn/rum
+npm install --save {{ PACKAGE_NAME }}/rum
 ```
 
 Or, using yarn:
 
 ```
-yarn add @xdn/rum
+yarn add {{ PACKAGE_NAME }}/rum
 ```
 
 Then, add the following to your application's browser bundle:
 
 ```js
-import { Metrics } from '@xdn/rum'
+import { Metrics } from '{{ PACKAGE_NAME }}/rum'
 
 new Metrics({
   token: 'your-token-here', // get this from https://moovweb.app
@@ -90,7 +90,7 @@ new Metrics({
 
 You can tie URLs to pages templates by providing an optional `router` parameter to `Metrics`.
 
-When installing @xdn/rum using a script tag, use:
+When installing {{ PACKAGE_NAME }}/rum using a script tag, use:
 
 ```js
 new XDN.Metrics({
@@ -105,11 +105,11 @@ new XDN.Metrics({
 }).collect()
 ```
 
-When installing @xdn/rum via NPM or Yarn use:
+When installing {{ PACKAGE_NAME }}/rum via NPM or Yarn use:
 
 ```js
-import { Router } from '@xdn/rum/Router'
-import { Metrics } from '@xdn/rum'
+import { Router } from '{{ PACKAGE_NAME }}/rum/Router'
+import { Metrics } from '{{ PACKAGE_NAME }}/rum'
 
 new Metrics({
   // get this from https://moovweb.app

guides/debugging.md

@@ -18,21 +18,21 @@ Edit the resulting configuration to look like this:
   "request": "launch",
   "cwd": "${workspaceFolder}",
   "autoAttachChildProcesses": true,
-  "program": "${workspaceFolder}/node_modules/@xdn/cli",
+  "program": "${workspaceFolder}/node_modules/{{ PACKAGE_NAME }}/cli",
   "args": ["run"]
 }
 ```
 
-The above assumes that the workspace folder is your app's root directory. If that is not the case, adjust `program` and `cwd` accordingly. The `program` config should always point to `@xdn/cli`. The `cwd` config should point to the root directory of your app.
+The above assumes that the workspace folder is your app's root directory. If that is not the case, adjust `program` and `cwd` accordingly. The `program` config should always point to `{{ PACKAGE_NAME }}/cli`. The `cwd` config should point to the root directory of your app.
 
 Note that this configuration will allow you to set breakpoints in both your XDN router as well as your application code (for example in Next.js, Nuxt.js, Angular, etc...).
 
 ## Cloud
 
 Your main tool in debugging XDN appplications that have been deployed are two sources of logs:
 
-* [Server logs](/guides/logs#section_server_logs)
-* [Access logs](/guides/logs#section_access_logs)
+- [Server logs](/guides/logs#section_server_logs)
+- [Access logs](/guides/logs#section_access_logs)
 
 Server logs will capture the output of your serverless in real time while access logs have complete traffic that is being served by your site including all the traffic that never reaches your serverless (e.g. cache hits, static assets, requests routed to custom backends, edge redirects, and so on).
 

guides/deploying.md

@@ -11,13 +11,13 @@ To deploy your site to {{ PRODUCT_NAME }}, you must first sign up for an account
 Next, globally install the XDN cli using npm:
 
 ```bash
-npm i -g @xdn/cli
+npm i -g {{ PACKAGE_NAME }}/cli
 ```
 
 Or using yarn:
 
 ```bash
-yarn global add @xdn/cli
+yarn global add {{ PACKAGE_NAME }}/cli
 ```
 
 ## xdn login