JavaScript: Difference between revisions

From Wildsong
Jump to navigationJump to search
Brian Wilson (talk | contribs)
Brian Wilson (talk | contribs)
mNo edit summary
 
(59 intermediate revisions by the same user not shown)
Line 1: Line 1:
Or maybe it's JavaScript, I can never keep it straight.
I will be developing new county GIS Web applications using [[OpenLayers]] and that means updating
my Web development skills with Javascript, React, Node and friends.
 
2019 was all about React but now I am jumping over to Svelte.
The irony is that I spent time learning React and am moving away from it just as Esri adopts it for Experience Builder.
So I will still be using React, but it won't be my focus.
 
== Read more books (and book-like things) ==
 
2022-01-28 Learning Svelte and Sveltekit. I still really like Parcel; should I use it or whatever Sveltekit does?
* Svelte https://svelte.dev/ and Sveltekit https://kit.svelte.dev/
* "Practical Svelte", Alex Libby, great book. https://learning.oreilly.com/library/view/practical-svelte-create/9781484273746/
 
2019-02-01
* "React In Action" and Redux in Action"
* "Building Enterprise JavaScript Applications"
 
* [https://github.com/getify/You-Dont-Know-JS You Don't Know JS] by Kyle Simpson (this is mostly true)
* [http://exploringjs.com/ Axel Rauschmayer's books] and [http://2ality.com/index.html blog]
* [http://eloquentjavascript.net Eloquent Javascript], 3rd edition by Marijn Haverbeke
* [https://www.andreasreiterer.at/ Andreas Reiterer's blog] has articles about React.
 
* [https://www.w3schools.com/ W3 Schools]
** [https://www.w3schools.com/jsref JavaScript reference]
** [https://www.w3schools.com/bootstrap Bootstrap 3 tutorial]
** lots more incl SQL, HTML, CSS, PHP, ...
* [https://hpbn.co/ High Performance Browser Networking]
* [https://nolanlawson.com/2017/01/09/how-to-write-a-javascript-package-for-both-node-and-the-browser/ How to write a JavaScript package...] and other blog posts
* Some books in Safari
** [https://0-proquest.safaribooksonline.com.marinet.lib.ca.us/book/programming/javascript/9781492067238 6 Javascript Projects] seems fun at first glance; includes HyperApp (chapter 4) and Parcel (chapter 5)
** [https://0-proquest.safaribooksonline.com.marinet.lib.ca.us/book/programming/javascript/9781788395540 Learning Node.js Development] may be out of date already
* or some as yet unidentified Node book, there are hundreds.
* I own a bunch of eBooks on JavaScript, HTML5, [[React]], etc.
 
* [https://www.manning.com/books/react-quickly React Quickly] is dated (eg React 15 instead of 16). (Skip it.)
 
== Svelte ==
 
Let's just break down and make a page right now, [[Svelte]].


I will be developing new county GIS Web applications using [[OpenLayers]] and that means updating
== React ==
my Web development skills with Node, Javascript, and friends.
 
I think I have a page for this, too. [[React]]
 
"Building Enterprise JavaScript Applications", see chapter 14
 
See the links at the bottom of this page
https://github.com/react-component/react-component.github.io
 
[https://www.fullstackreact.com/articles/how-to-write-a-google-maps-react-component/ Google maps in React]
 
=== Redux ===
 
Maybe you don't need to know anything about Redux and can instead use contexts! That would be nice.
https://blog.bitsrc.io/react-context-api-a-replacement-for-redux-6e20790492b3
 
Or maybe there are still reasons to use Redux: http://davidandsuzi.com/writing-a-basic-react-redux-app-in-2018/
Note the author says it's based on an article from 2015. ;-)
 
=== Ole port ===
 
I forked [https://github.com/brian32768/ole Ole] from its
[https://github.com/boundlessgeo/ole Boundless past] to 2018,
and writing about that process in my new [https://github.com/brian32768/ole/wiki Github Wiki].
 
=== Stupid caniuse-lite error ===
 
It suggests an npm command to fix it but the command does nothing.
This has been bugging me for months. The fix is
 
npx browserslist@latest --update-db
 
=== Look at more ===
* [[Web APIs]] and JavaScript generally seem to go together.
* [[Bootstrap]] (need to work on this page)
* [[OpenLayers]] (duh)
* [[Parcel Bundler]]
 
=== Things to look at soonish ===


== Using Parcel bundler ==
* Geolocation: See "HTML5 and JavaScript Web Apps", chapter 7.
* Device Orientation API: "HTML5 and JavaScript Web Apps", chapter  8. Accelerometers, compasses, etc.


Runs code, does "hot module replacement", you can watch what's happening... beautiful.
=== Using but don't want to know about ===
* jquery
* babel - An Ole dependency that translates JS code


Except - does not work in Visual Studio -- it does not always see changes. Occasionally it does, I get excited, then it stops.
=== Things to ignore for now ===
* Ionic cross platform build thingie https://www.javascripttuts.com/the-ionic-build-process-tutorial/
* Grunt, Bower, Yeoman
* browserify, browserify-derequire, browserify-header
* Angular, Dojo,  
* 150 other app frameworks


Does not work with Emacs until you turn off autobackup files with this in your .emacs:
== Using Node ==


(setq make-backup-files nil)
There is a nice blog post here that explains all the stuff I learned painfully slowly over the last month.
Read the first part, stop reading when you get to the section on Bower. Time has marched on and now there is Parcel.


I like backup files but I like '''hot module replacement''' even more.
[[Node]] was originally intended to be for server side Javascript but ends up being a great development tool for client side applications.
I have not actually used it on a server yet.


== Using Visual Studio ==
== Parcel builder ==


Currently I am using [[Microsoft Visual Studio]]. Visual Studio Code looks nice but I don't feel a need to develop new skills right now.
Automatically creates bundles and runs your app, does "hot module replacement", you can watch what's happening... beautiful. When you edit+save that Parcel sees the file change and triggers a rebuild. Sometimes I have to hit refresh in the browser.
One IDE to rule them all and in the darkness bind them! Uh yeah.


I installed the Node.JS workload in VS
Except - does not work in Visual Studio -- after saving from VS, Parcel does not always see changes. Occasionally it does, I get excited, then it stops. I switched to [[Atom]] anyway.
and installed the (standalone) portable Node.JS package.


Now in VS I can create a web Node.JS project, and I can run and test the complete app on my desktop so I don't need any access to a real web server.
=== Install it ===


In my VS project, I have to set the Node.exe path to C:\Users\bwilson\Portable\node-v8.11.3-win-x64\node.exe
npm install -g parcel-bundler
Once I do that it can find the other tools like npm too.


My typical server.js looks like this; I keep it in a VS template at github to make project creation easier.
Add to PATH C:/Users/bwilson/AppData/Roaming/npm


<pre>
=== Parcel + Emacs ===
var http = require('http');
var port = process.env.PORT || 1337;
var path = require('path'),
    fs = require('fs');
var base = 'C:/GeoModel/WebMaps/OpenlayersApp';


http.createServer(function (req, res) {
Parcel HMR does not work with Emacs until you turn off autobackup files with this in your .emacs:
   
    pathname = base + req.url;
    if (req.url === '/') {
        pathname = base + '/index.html';
    }
    console.log(pathname);


    if (fs.exists(pathname)) {
(setq make-backup-files nil)
        res.writeHead(404);
        res.write('Page not found 404\n');
        res.end();
    } else {
        res.setHeader('Content-Type', 'text/html');
        res.statusCode = 200;
        var file = fs.createReadStream(pathname);
        file.on("open", function () {
            file.pipe(res);
        });
    }


}).listen(port);
I like backup files but I like '''hot module replacement''' even more.


console.log("Server running on port ", port);
=== Building a standalone package ===
</pre>


When I run the project, it launches server js and in turn launches a browser and serves up my index.html. I can click local links therein.
Okay but if I am NOT building an app and instead want to build a standalone module and want to test it in Parcel,
I can edit the index.html and hit reload in the browser and ta-da! there's my updated page.
how do I do that? I think I should look at https://parceljs.org/packagers.html


=== Debugging the client ===
== Which IDE for JavaScript? ==  


Currently I use Parcel (which is based on node). Running node is another option.
VS Code won out on this, deleting all the old comments here! Just use VS Code.
Basically either way you run a tiny server on your desktop and watch output in a cmd window.


==== Parcel ====
Forget Atom and Visual Studio and whatever thing comes from JetBrains.


Parcel gives you "hot module replacement" and you don't have to write and maintain a server.js, the server is built in.
Parcel gives you "hot module replacement" and you don't have to write and maintain a server.js, the server is built in.


I have a script set up in package.json to launch parcel and it in turn launches a chrome browser. In a cmd window I type
I have a script set up in package.json to launch parcel and it in turn launches a browser. In a '''cmd''' window I type
 
npm start
 
Running "npm run build" creates a deployment bundle in the dist/ folder, copy that to a server and voila! Deployed.
 
== ESLint ==
 
YAY lint. I can run "npm run lint" to get output all at once in a terminal window
and I can leave fast-eslint turned on all the time in atom to get help while editing.
 
In npm I installed globally


  npm test
  npm install eslint -g


Running "npm run-script build" creates a deployment bundle in the dist/ folder, copy that to a server and voila! Deployed.
and in each project needing lint I installed
npm install eslint-plugin-import -D
npm install eslint-plugin-node -D
npm install eslint-plugin-promise -D
npm install eslint-plugin-react -D
npm install eslint-plugin-react-hooks -D
npm install eslint-plugin-standard -D
npm install eslint-config-standard -D
npm install eslint-config-standard-react -D


==== Node ====
In Atom I installed
apm install fast-eslint
 
My .eslint.js file looks like
<pre>
module.exports = {
    "env": {
        "browser": true,
        "es6": true
    },
    "extends": ["eslint:recommended"],
    "globals": {
        "Atomics": "readonly",
        "SharedArrayBuffer": "readonly"
    },
    "parserOptions": {
        "ecmaFeatures": {
            "jsx": true
        },
        "ecmaVersion": 2018,
        "sourceType": "module"
    },
    "plugins": [
        "react",
"react-hooks"
    ],
    "rules": {
"react-hooks/rules-of-hooks": "error",
        "react-hooks/exhaustive-deps": "warn"
    }
};
</pre>
 
My .eslintignore file looks like
<pre>
tasks/
dist/
build/
node_modules/
</pre>


Refer to https://docs.microsoft.com/en-us/visualstudio/debugger/client-side-script-debugging
I add this line to scripts in package.json
"lint": "eslint .",


NOTE if you have 15.7 installed: [https://blogs.msdn.microsoft.com/webdev/2018/06/29/changes-to-script-debugging-in-visual-studio-15-7/ Change in 15.7]
== Some links ==


I was able to change my default browser to IE and get that going. Good news.
* [https://juristr.com/blog/2014/08/node-grunt-yeoman-bower/ Blog about Node]
Now I need to make it work in Chrome, this guy's page helped me:  
* [https://parceljs.org/getting_started.html Parcel docs]
[http://lostindetails.com/blog/post/JavaScript-debugging-in-VisualStudio-with-Chrome JavaScript debugging in VisualStudio with Chrome]
* [http://speakingjs.com/ Speaking Javascript] : An In-Depth Guide for Programmers by Dr. Axel Rauschmayer
and [https://chromedevtools.github.io/devtools-protocol/ Chrome's page on the subject.]
* [http://eloquentjavascript.net Eloquent Javascript, third edition] Written by Marijn Haverbeke. 3rd edition comes out in print in November 2018
* [http://bonsaiden.github.com/JavaScript-Garden JavaScript Garden]
* JavaScript Pocket Reference (O'Reilly)


# Start chrome in remote debug mode: chrome.exe --remote-debugging-port=9222
[[Category: JavaScript]]
# Attach Visual Studio: "Debug" -> "Attach to Process..." -> select the chrome instance
[[Category: Web]]
Done.

Latest revision as of 16:21, 24 March 2022

I will be developing new county GIS Web applications using OpenLayers and that means updating my Web development skills with Javascript, React, Node and friends.

2019 was all about React but now I am jumping over to Svelte. The irony is that I spent time learning React and am moving away from it just as Esri adopts it for Experience Builder. So I will still be using React, but it won't be my focus.

Read more books (and book-like things)

2022-01-28 Learning Svelte and Sveltekit. I still really like Parcel; should I use it or whatever Sveltekit does?

2019-02-01

  • "React In Action" and Redux in Action"
  • "Building Enterprise JavaScript Applications"

Svelte

Let's just break down and make a page right now, Svelte.

React

I think I have a page for this, too. React

"Building Enterprise JavaScript Applications", see chapter 14

See the links at the bottom of this page https://github.com/react-component/react-component.github.io

Google maps in React

Redux

Maybe you don't need to know anything about Redux and can instead use contexts! That would be nice. https://blog.bitsrc.io/react-context-api-a-replacement-for-redux-6e20790492b3

Or maybe there are still reasons to use Redux: http://davidandsuzi.com/writing-a-basic-react-redux-app-in-2018/ Note the author says it's based on an article from 2015. ;-)

Ole port

I forked Ole from its Boundless past to 2018, and writing about that process in my new Github Wiki.

Stupid caniuse-lite error

It suggests an npm command to fix it but the command does nothing. This has been bugging me for months. The fix is

npx browserslist@latest --update-db

Look at more

Things to look at soonish

  • Geolocation: See "HTML5 and JavaScript Web Apps", chapter 7.
  • Device Orientation API: "HTML5 and JavaScript Web Apps", chapter 8. Accelerometers, compasses, etc.

Using but don't want to know about

  • jquery
  • babel - An Ole dependency that translates JS code

Things to ignore for now

Using Node

There is a nice blog post here that explains all the stuff I learned painfully slowly over the last month. Read the first part, stop reading when you get to the section on Bower. Time has marched on and now there is Parcel.

Node was originally intended to be for server side Javascript but ends up being a great development tool for client side applications. I have not actually used it on a server yet.

Parcel builder

Automatically creates bundles and runs your app, does "hot module replacement", you can watch what's happening... beautiful. When you edit+save that Parcel sees the file change and triggers a rebuild. Sometimes I have to hit refresh in the browser.

Except - does not work in Visual Studio -- after saving from VS, Parcel does not always see changes. Occasionally it does, I get excited, then it stops. I switched to Atom anyway.

Install it

npm install -g parcel-bundler

Add to PATH C:/Users/bwilson/AppData/Roaming/npm

Parcel + Emacs

Parcel HMR does not work with Emacs until you turn off autobackup files with this in your .emacs:

(setq make-backup-files nil)

I like backup files but I like hot module replacement even more.

Building a standalone package

Okay but if I am NOT building an app and instead want to build a standalone module and want to test it in Parcel, how do I do that? I think I should look at https://parceljs.org/packagers.html

Which IDE for JavaScript?

VS Code won out on this, deleting all the old comments here! Just use VS Code.

Forget Atom and Visual Studio and whatever thing comes from JetBrains.

Parcel gives you "hot module replacement" and you don't have to write and maintain a server.js, the server is built in.

I have a script set up in package.json to launch parcel and it in turn launches a browser. In a cmd window I type

npm start

Running "npm run build" creates a deployment bundle in the dist/ folder, copy that to a server and voila! Deployed.

ESLint

YAY lint. I can run "npm run lint" to get output all at once in a terminal window and I can leave fast-eslint turned on all the time in atom to get help while editing.

In npm I installed globally

npm install eslint -g 

and in each project needing lint I installed

npm install eslint-plugin-import -D
npm install eslint-plugin-node -D
npm install eslint-plugin-promise -D
npm install eslint-plugin-react -D
npm install eslint-plugin-react-hooks -D
npm install eslint-plugin-standard -D
npm install eslint-config-standard -D
npm install eslint-config-standard-react -D

In Atom I installed

apm install fast-eslint

My .eslint.js file looks like

module.exports = {
    "env": {
        "browser": true,
        "es6": true
    },
    "extends": ["eslint:recommended"],
    "globals": {
        "Atomics": "readonly",
        "SharedArrayBuffer": "readonly"
    },
    "parserOptions": {
        "ecmaFeatures": {
            "jsx": true
        },
        "ecmaVersion": 2018,
        "sourceType": "module"
    },
    "plugins": [
        "react",
	"react-hooks"
    ],
    "rules": {
	"react-hooks/rules-of-hooks": "error",
        "react-hooks/exhaustive-deps": "warn"
    }
};

My .eslintignore file looks like

tasks/
dist/
build/
node_modules/

I add this line to scripts in package.json

"lint": "eslint .",

Some links