loopbackio / loopbackio/loopback-next
[@loopback/build] not copying non-TypeScript files with --copy-resources flag from v9.0.10
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.1k
- Forks
- 1.1k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 27
Description
### Describe the bug
Hello,
It's not a best practice but in a few use cases we need to copy non-Typescript files when building a project.
For this reason with TypeScript we have the option to use --copy-resources with LB Build package.
lb-tsc --copy-resources
Although from loopback/build v9.0.10 non-TypeScript files are not copied. This breaks the code in some scenarios as files are not found.
PS: I will try to find a time to figure out the root cause but if anyone has any idea please let us know.
BR,
Harshal
### Logs
_No response_
### Additional information
_No response_
### Reproduction
.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the lb-tsc entry point in @loopback/build and trace handling of the --copy-resources flag. Reproduce the reported behavior with a project containing non-TypeScript files, then verify that those resources are copied during the build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100