Environment, script - Githubissues

develop-mental-llc / create-react-admin-amplify-app

2 stars 0 forks source link

Environment, script #9

Closed tcodes0 closed 2 years ago

tcodes0 commented 4 years ago

fix #8

tcodes0 commented 4 years ago

Added linter, formatter, configured jest and commit hooks for linting and formatting on commit.

tcodes0 commented 4 years ago

fix #10

See file src/bootstrap.ts for script implementation. Amplify requires interaction by default to set up, I think this is fine for now, although expect could work to automate it, but I'm not sure, kinda complex.

To test the script:

clone repo
npm install
npm run dev

It will execute the script in your terminal. Passing the name of the app using the command line is supported. npm run dev myApp Flags -h and --help are supported.

still working on amplify & steps after that, think we can get a basic version going pretty soon

DCarper commented 4 years ago

See file src/bootstrap.ts for script implementation. Amplify requires interaction by default to set up, I think this is fine for now, although expect could work to automate it, but I'm not sure, kinda complex.

Lets keep thinking about this. My thought at this point is that would be building a wrapper for Amplify itself which I think should be beyond the scope of craaa, devs will still need to learn and use amplify-cli for ongoing development.

We need a good vision statement for this package...

tcodes0 commented 4 years ago

install loop and yarn removed here

fix #11 just need to add webpack now

tcodes0 commented 4 years ago

Ok, this should be the early MVP with the happy path working. To test

To test the script:
- clone repo
- `npm install`
- npm run dev

expect to cd to project, run npm run start and it should show the RAA dashboard.

tcodes0 commented 4 years ago

We should create the app outside of the repo to avoid weirdness with git and npm, for now installing it in the directory containing the craaa repo would be great

We currently use create-react-app to make the folder and the bulk of the files, so I think that's already how it works OR I'm misunderstanding.

Can we please remove anything to do with yarn?

~yep, my bad.~ The lock file is not in the PR nor on my local repo, must be local to you then. Yarn's future is a bit gray right now, some influential devs in the JS community even declared it dead... shame though, really good cli