今天
飲食正常，晚上有吃水果。
金錢使用正常。
有背一些英文單字，但是日文還沒開始看。
有在家簡單的活動一下。
睡眠時間為 2:00 ，不如預期，明天改進。
特別
今天對時間的利用比較充分，沒有太多的發呆時間，做的滿緊湊充實的。
找出 SQL Server sa account、password setup 的方法。
對明天的期望
好的維持
提早睡眠時間
Use NVM to handle Angular-Node.js incompatibility (e.g., Uncaught SyntaxError: Unexpected token 'export')
Overview If you are a fullstack developer, the chances are that you will be creating multiple frontend or Node.js projects along the way. When you are creating new projects using the newest version of the cli (command-line interface) of a particular framework, you might be asked to install the most updated version of Node.js in order to utilize the newest feature. This might involve upgrading your Node.js version, which might not be compatible with other existing projects (e.g., using Angular) you have created before. A potential solution is to use nvm (Node Version Manager) to install multiple versions of Node.js and use a particular version of the Node.js to install the proper version of the cli (e.g., Angular-CLI) that can be used to manage a particular project. Here I will use a problem I run into to explain how to solve it. Problem There is a compatibility issue between Node.js and angular.js. For instance, I run into an error when I was using an incompatible version of Node.js ...
Comments