@vmfvmf/jtc
v1.4.29
Published
Schematics to generate a new frontend/backend
Downloads
2,036
Readme
The argument p2b refers to the files in the folder project-to-build, but it must omit the .js on the arg
After edition on project run 'npm run build:package' to update de compilation
To create the entire project schematics .:new-project --debug=true --prjid=1
To create backend, run: schematics .:new-backend --debug=false --prjid=1
To create frontend, run: schematics .:new-frontend --debug=false --prjid=1
To create backend uc run: schematics .:add-backend-artifacts --debug=false --prjid=1
To create frontend component run: schematics .:add-frontend-artifacts --debug=false --ucfid=1
PUBLISHING: in a project, first execute 'npm init --scope=@vmfvmf' to initialize a npm project then execute 'npm adduser' to add a user from npm finally 'npm publish' to publish to npm
after, published and installed locally, its possible to run:
ng new --collection @vmfvmf/jtc --prjid=1 ng g @vmfvmf/jtc:new-backend --prjid=1 schematics @vmfvmf/jtc:new-backend --prjid=1
TO run specifics add, the project exist in the jtc-output folder.
schematics .:add-frontend-artifacts --ucfid=12 --debug=false
ng generate or g need to be executed inside a angular project, so it cant be executed on a java project
errors: schematics is unknown: npm install -g @angular-devkit/schematics-cli