...
...
...
...
Table of Contents |
---|
Child pages
Child pages (Children Display) |
---|
Dumping ground for stuff to be organized:
...
...
Books
- Beginner books:
- Amazon - JavaScript for Beginners
- rec'd by Patrick here
- Amazon - A Smarter Way to Learn JavaScript
- very. very high reviews
- Alright, I bought it and it's for total beginners to programming. It's probably a waste of my time to go through it.
- Amazon - JavaScript for Beginners
- Intermediate books
- Human JavaScript
- rec'd by Christian O. at Inf.
- 2016 - Amazon - Secrets of the JavaScript Ninja
- rec'd by Patrick here
- Human JavaScript
- Advanced books
...
- 2015.04.14 - WebAppLog.com - To Engineers Who Tried to Use Jade Template Engine and Can’t Get Started
- This looks pretty useful.
Node
npm
- An explanation I wrote of how to read and resolve npm dependency conflict errors: https://stackoverflow.com/a/77504180/4115031
- Stack Overflow - How do I update each dependency in package.json to the latest version?
- To upgrade to the latest version of npm on Windows, I can run
npm-windows-upgrade --npm-version latest
- This only works because I installed the
npm-windows-upgrade
tool as explained here.
- This only works because I installed the
Webpack
Tutorials / courses
...
ERROR in ./src/main.js
Module build failed: Error: Failed to load plugin node: Cannot find module 'eslint-plugin-node'
- How I fixed it:
npm install --save-dev eslint-plugin-node
- Basically I just looked at my package.json and saw that "eslint-plugin-node" wasn't listed in my devDependencies, so I guessed adding it there would fix the error.
- How I fixed it:
Module build failed: SyntaxError: Unexpected token (
- On 2018.03.03 I got this error because I had a lot of code in my app.html (the main HTML file used by the Webpack project) that was commented out using Jinja2-style comments (so,
{# ... #}
). When I got rid of the code that was commented-out like that, the error message went away.
- On 2018.03.03 I got this error because I had a lot of code in my app.html (the main HTML file used by the Webpack project) that was commented out using Jinja2-style comments (so,
With Jinja2 template code
- Any Jinja2 code that I have in a single-file template (.vue file) does not get rendered by Flask, because that code is never put into the app.html, but is instead located within a JavaScript file (app.js) that is loaded into that HTML file after the page has already been rendered and served to the client.