This PR builds on #4 , in adding code to remix.init that will "un-ignore" the lockfile. This happens in 2 two places:
.gitignore
deply.yml workflow
This is because the stack itself is effectively a library, and doesn't need a lockfile. Additionally, we do not know which package manager the user will decide to use when initializing the stack.
Once the stack is initialized though, it "becomes" an application, and it should commit a lockfile, and then enforce as part of CI, as it is best practice. So by "un-ignoring" the lockfile on initilization, we encourage that best practice for applications.
Closes #5
This PR builds on #4 , in adding code to
remix.initthat will "un-ignore" the lockfile. This happens in 2 two places:gitignoredeply.ymlworkflowThis is because the stack itself is effectively a library, and doesn't need a lockfile. Additionally, we do not know which package manager the user will decide to use when initializing the stack.
Once the stack is initialized though, it "becomes" an application, and it should commit a lockfile, and then enforce as part of CI, as it is best practice. So by "un-ignoring" the lockfile on initilization, we encourage that best practice for applications.