1619403550
Today I will share my journey in regards to how I migrated my existing Wordpress website to Next JS with Cosmic JS. Use the Jamstac in 2021
Cosmic JS: https://www.cosmicjs.com/
Next Js Examples: https://github.com/vercel/next.js/tree/canary/examples
#wordpress #next #react #cosmic
1632537859
Not babashka. Node.js babashka!?
Ad-hoc CLJS scripting on Node.js.
Experimental. Please report issues here.
Nbb's main goal is to make it easy to get started with ad hoc CLJS scripting on Node.js.
Additional goals and features are:
Nbb requires Node.js v12 or newer.
CLJS code is evaluated through SCI, the same interpreter that powers babashka. Because SCI works with advanced compilation, the bundle size, especially when combined with other dependencies, is smaller than what you get with self-hosted CLJS. That makes startup faster. The trade-off is that execution is less performant and that only a subset of CLJS is available (e.g. no deftype, yet).
Install nbb
from NPM:
$ npm install nbb -g
Omit -g
for a local install.
Try out an expression:
$ nbb -e '(+ 1 2 3)'
6
And then install some other NPM libraries to use in the script. E.g.:
$ npm install csv-parse shelljs zx
Create a script which uses the NPM libraries:
(ns script
(:require ["csv-parse/lib/sync$default" :as csv-parse]
["fs" :as fs]
["path" :as path]
["shelljs$default" :as sh]
["term-size$default" :as term-size]
["zx$default" :as zx]
["zx$fs" :as zxfs]
[nbb.core :refer [*file*]]))
(prn (path/resolve "."))
(prn (term-size))
(println (count (str (fs/readFileSync *file*))))
(prn (sh/ls "."))
(prn (csv-parse "foo,bar"))
(prn (zxfs/existsSync *file*))
(zx/$ #js ["ls"])
Call the script:
$ nbb script.cljs
"/private/tmp/test-script"
#js {:columns 216, :rows 47}
510
#js ["node_modules" "package-lock.json" "package.json" "script.cljs"]
#js [#js ["foo" "bar"]]
true
$ ls
node_modules
package-lock.json
package.json
script.cljs
Nbb has first class support for macros: you can define them right inside your .cljs
file, like you are used to from JVM Clojure. Consider the plet
macro to make working with promises more palatable:
(defmacro plet
[bindings & body]
(let [binding-pairs (reverse (partition 2 bindings))
body (cons 'do body)]
(reduce (fn [body [sym expr]]
(let [expr (list '.resolve 'js/Promise expr)]
(list '.then expr (list 'clojure.core/fn (vector sym)
body))))
body
binding-pairs)))
Using this macro we can look async code more like sync code. Consider this puppeteer example:
(-> (.launch puppeteer)
(.then (fn [browser]
(-> (.newPage browser)
(.then (fn [page]
(-> (.goto page "https://clojure.org")
(.then #(.screenshot page #js{:path "screenshot.png"}))
(.catch #(js/console.log %))
(.then #(.close browser)))))))))
Using plet
this becomes:
(plet [browser (.launch puppeteer)
page (.newPage browser)
_ (.goto page "https://clojure.org")
_ (-> (.screenshot page #js{:path "screenshot.png"})
(.catch #(js/console.log %)))]
(.close browser))
See the puppeteer example for the full code.
Since v0.0.36, nbb includes promesa which is a library to deal with promises. The above plet
macro is similar to promesa.core/let
.
$ time nbb -e '(+ 1 2 3)'
6
nbb -e '(+ 1 2 3)' 0.17s user 0.02s system 109% cpu 0.168 total
The baseline startup time for a script is about 170ms seconds on my laptop. When invoked via npx
this adds another 300ms or so, so for faster startup, either use a globally installed nbb
or use $(npm bin)/nbb script.cljs
to bypass npx
.
Nbb does not depend on any NPM dependencies. All NPM libraries loaded by a script are resolved relative to that script. When using the Reagent module, React is resolved in the same way as any other NPM library.
To load .cljs
files from local paths or dependencies, you can use the --classpath
argument. The current dir is added to the classpath automatically. So if there is a file foo/bar.cljs
relative to your current dir, then you can load it via (:require [foo.bar :as fb])
. Note that nbb
uses the same naming conventions for namespaces and directories as other Clojure tools: foo-bar
in the namespace name becomes foo_bar
in the directory name.
To load dependencies from the Clojure ecosystem, you can use the Clojure CLI or babashka to download them and produce a classpath:
$ classpath="$(clojure -A:nbb -Spath -Sdeps '{:aliases {:nbb {:replace-deps {com.github.seancorfield/honeysql {:git/tag "v2.0.0-rc5" :git/sha "01c3a55"}}}}}')"
and then feed it to the --classpath
argument:
$ nbb --classpath "$classpath" -e "(require '[honey.sql :as sql]) (sql/format {:select :foo :from :bar :where [:= :baz 2]})"
["SELECT foo FROM bar WHERE baz = ?" 2]
Currently nbb
only reads from directories, not jar files, so you are encouraged to use git libs. Support for .jar
files will be added later.
The name of the file that is currently being executed is available via nbb.core/*file*
or on the metadata of vars:
(ns foo
(:require [nbb.core :refer [*file*]]))
(prn *file*) ;; "/private/tmp/foo.cljs"
(defn f [])
(prn (:file (meta #'f))) ;; "/private/tmp/foo.cljs"
Nbb includes reagent.core
which will be lazily loaded when required. You can use this together with ink to create a TUI application:
$ npm install ink
ink-demo.cljs
:
(ns ink-demo
(:require ["ink" :refer [render Text]]
[reagent.core :as r]))
(defonce state (r/atom 0))
(doseq [n (range 1 11)]
(js/setTimeout #(swap! state inc) (* n 500)))
(defn hello []
[:> Text {:color "green"} "Hello, world! " @state])
(render (r/as-element [hello]))
Working with callbacks and promises can become tedious. Since nbb v0.0.36 the promesa.core
namespace is included with the let
and do!
macros. An example:
(ns prom
(:require [promesa.core :as p]))
(defn sleep [ms]
(js/Promise.
(fn [resolve _]
(js/setTimeout resolve ms))))
(defn do-stuff
[]
(p/do!
(println "Doing stuff which takes a while")
(sleep 1000)
1))
(p/let [a (do-stuff)
b (inc a)
c (do-stuff)
d (+ b c)]
(prn d))
$ nbb prom.cljs
Doing stuff which takes a while
Doing stuff which takes a while
3
Also see API docs.
Since nbb v0.0.75 applied-science/js-interop is available:
(ns example
(:require [applied-science.js-interop :as j]))
(def o (j/lit {:a 1 :b 2 :c {:d 1}}))
(prn (j/select-keys o [:a :b])) ;; #js {:a 1, :b 2}
(prn (j/get-in o [:c :d])) ;; 1
Most of this library is supported in nbb, except the following:
:syms
.-x
notation. In nbb, you must use keywords.See the example of what is currently supported.
See the examples directory for small examples.
Also check out these projects built with nbb:
See API documentation.
See this gist on how to convert an nbb script or project to shadow-cljs.
Prequisites:
To build:
bb release
Run bb tasks
for more project-related tasks.
Download Details:
Author: borkdude
Download Link: Download The Source Code
Official Website: https://github.com/borkdude/nbb
License: EPL-1.0
#node #javascript
1626693995
WordPress has remained a preferred choice of thousands of entrepreneurs worldwide. WordPress powers approximately 64 million websites, and over 400 million people visit WordPress sites every month globally. In such a scenario, it is beneficial to migrate your existing website to the WordPress platform. Transferring or moving any website from one web host to another web host or transferring an existing web platform to another one is known as “Website Migration“.
Moving your website from Namecheap to Hostinger is an example of Migrating web hosts, and moving your website from one CMS (Content Management System) to another is an example of migrating web platforms. Transferring your website from Joomla to WordPress is known as the migration of web platforms.
Let’s go through the key reasons why you should opt for a WordPress migration service. But, before moving to the benefits, let’s understand about WordPress migration service.
What Is WordPress Migration Service?
A provider who migrates your existing website to WordPress on your behalf is called a WordPress migration service provider. In other words, your website’s files, data, and domain are moved from one server to another during its migration to WordPress. Though it sounds simple, WordPress developers have to meet various protocols and follow the complicated processes for file configuration and redirections while migrating the website to WordPress.
8 Benefits Of Using WordPress Migration Service
Here we have mentioned eight major benefits of WordPress migration for your existing individual or business website. It will help you get the answer to why you should migrate to WordPress.
1. To Avoid Downtime
Web hosting has a huge role to play in the loading speed of the website. If any website loads in 3 seconds or more, then 16% of the clients are lost. What’s more, about 40% of the visitors leave that website and switch to another site. In a way, the slow loading of the website is a major obstacle to the success of a website.
Website speed also affects SEO. Slow-loading websites are not very SEO-friendly and get less web traffic as compared to their counterparts. We can mention various reasons for the slowdown of your website. A poorly configured hosting server may be the first. The other could be shared hosting servers which lead to an overcrowded server.
This problem might be resolved to an extent by using the WordPress migration service.
2. To Overcome Technical Issues
At times, your website goes down because many visitors come to it at once. This issue indicates that your web hosting is not so active. In such a scenario, it is better to migrate your business website to an active and robust host.
Backing up data is very important. If your existing hosting provider does not offer a daily backups facility, it is time to explore the one that offers it. WordPress website migration service can assist you to resolve such technical issues.
3. To Remove Sluggishness Of Dashboard
We have already discussed the impact of slow websites on customers. Similarly, it is frustrating for the owner of the website if its dashboard works at a slow speed. The slow dashboard can also waste your valuable time and you may not focus on other productive activities.
WordPress Dashboard has a robust control panel for managing a complete website. Simply put, you can opt for a migration service to WordPress to remove the sluggishness of the dashboard.
4. To Save Time And Hassle
In theory, doing a site migration yourself saves you money, time, and hassle. But, in reality, not outsourcing this task to a WordPress migration service provider means the opposite!
Imagine how many hours this would take you:
Now that your time has been spent on all those things, you have wasted money too.
Therefore, it is better to hire WordPress developers from a reputed company to get the job done in some days.
Plus, a professional WordPress website migration service works neatly and keeps your site running with little or no downtime.
Your job is to grow your business, not becoming a WordPress techie. Trying to do a site migration takes too much of your time and brings many hassles. Therefore, it is better to outsource the website migration.
Read the rest of this article here.
#wordpress migration #wordpress migration services #wordpress tips #wordpress website migration #wordpress website
1619403550
Today I will share my journey in regards to how I migrated my existing Wordpress website to Next JS with Cosmic JS. Use the Jamstac in 2021
Cosmic JS: https://www.cosmicjs.com/
Next Js Examples: https://github.com/vercel/next.js/tree/canary/examples
#wordpress #next #react #cosmic
1625674200
In this video, we are going to implement Google Analytics to our Next JS application. Tracking page views of an application is very important.
Google analytics will allow us to track analytics information.
Frontend: https://github.com/amitavroy/video-reviews
API: https://github.com/amitavdevzone/video-review-api
App link: https://video-reviews.vercel.app
You can find me on:
Twitter: https://twitter.com/amitavroy7
Discord: https://discord.gg/Em4nuvQk
#next js #js #react js #react #next #google analytics
1594166040
The moving of applications, databases and other business elements from the local server to the cloud server called cloud migration. This article will deal with migration techniques, requirement and the benefits of cloud migration.
In simple terms, moving from local to the public cloud server is called cloud migration. Gartner says 17.5% revenue growth as promised in cloud migration and also has a forecast for 2022 as shown in the following image.
#cloud computing services #cloud migration #all #cloud #cloud migration strategy #enterprise cloud migration strategy #business benefits of cloud migration #key benefits of cloud migration #benefits of cloud migration #types of cloud migration