refactor: ensures dependencies are up-to-date

[BWsix]

Fixes https://github.com/line/create-liff-app/issues/11

This PR changes how create-liff-app install dependencies, ensuring that all dependencies used in generated projects are up-to-date. I'm not sure if this is fixing the issue or making it even worse, any feedback would be great🙏

Changes:

• .eslinerc.js
  • removed 'linebreak-style': ['error', 'unix'] since all the linebreaks are in CRLF
• removed dependencies and devDependencies fields in every package.json in /templates (except for nuxtjs templates)
• removed @line/create-liff-app upgradation script
• create-liff-app.ts
  • added templates object in the end of the file to store all the dependencies used by different frameworks
  • moved envPrefix and envFileNameVariants into templates object
  • install function now installs dependencies from templates object in runtime

Problems that need to be discussed:

• (not related to this PR) nuxtjs projects generated by the current version(1.0.4) of create-liff-app do not work as expected, as it always throws this error: Error: liffId is necessary for liff.init(). I do not know how to fix that.
• under the current refactor, when a user selects no on the question install now, create-liff-app will first run npm install --package-lock-only to install the latest version of the packages without actually saving them to the node_modules, then use fs.rmSync to delete the generated package-lock.json. I do not think this is a good way of handling the problem and maybe it needs to be replaced? Below are two possible fixes that I came up with. What do you think?
  • remove the install now option and install the dependencies by default list create-next-app does. This is lesserror-prone.
  • bring back dependencies and devDependencies fields in every package.json in /templates. Use them to generate outdated dependencies as it does in the current version(1.0.4) of create-liff-app, then remind the user to upgrade the dependencies in the showDoneComments function.

Notes:

• Nuxtjs
  • dependencies used in create-nuxt-app are hardcoded into package.json, so this refactor followed the conversion and only @line/liff is installed in the runtime

[BWsix]

Since Nuxtjs and Nextjs provide their own create-app feature, how do you think using them inside create-liff-app and replacing the result with our templates?

I did some changes (https://github.com/line/create-liff-app/pull/15/commits/c406a40b82db1ffac6a30553329bc0f6d239ce8f) and create-liff-app will now generate nextjs & nuxtjs projects using their create-app feature. Does this look ok to you?

Changes:

• after users answer the questions, create-liff-app will now generate nextjs / nuxtjs project using create-app. Then, create-liff-app will use its template to overwrite the generated files.
• removed most of the files in /templates/nextjs & /templates/nuxtjs since they are the same as the create-app generated ones.

nuxtjs projects generated by the current version(1.0.4) of create-liff-app do not work as expected, as it always throws this error: Error: liffId is necessary for liff.init(). I do not know how to fix that.

Also, as I mentioned in the original PR, nuxtjs app does not work as expected. Therefore, I am unsure if the above change will break anything. Please remember to double-check the changes!

[BWsix]

let us set up CI to automatically test and lint before merging

Please help me out on this one, as I do not know how😅

[BWsix]

Thank you and your team for the time and effort you spent reviewing this PR👍

[so99ynoodles]

Maybe we should fix the test since the local test fails. yarn test

[so99ynoodles]

Merging this! 🎉