ASP.NET Core with Aurelia-CLI and RequireJS does not create .NET Core project
- Dominant language
- JavaScript
- Stars
- 402
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Description
**I'm submitting a bug report**
* **Library Version:**
aurelia-cli v1.0.0-beta.9
**Please tell us about your environment:**
* **Operating System:**
Windows 10
* **Node Version:**
v10.13.0
* **Yarn Version:**
1.13.0
* **Browser:**
all
* **Language:**
TypeScript 3
* **Loader/bundler:**
RequireJS
**Current behavior:**
When following options for new Aurelia CLI project are choosen:
> Name: my-app
> Platform: ASP.NET Core
> Bundler: Aurelia-CLI
> Loader: RequireJS
> Transpiler: TypeScript
> Markup Processor: Minimal Minification
> CSS Processor: None
> Unit Test Runner: Jest
> Integration Test Runner: Protractor
> Editor: Visual Studio Code
Aurelia CLI creates simple Web project which uses browserSync (`au run`) to run. There is no single ASP.NET Core/C# file in the folder.
* **What is the expected behavior?**
Aurelia CLI should create .NET Core project which can be run using `dotnet run`, similar to option with WebPack bundler.
* **What is the motivation / use case for changing the behavior?**
It's a bug.
Contributor guide
Research direction
Reproduce the issue using the listed Aurelia CLI choices, especially ASP.NET Core with Aurelia-CLI, RequireJS, and TypeScript. Inspect the CLI project-generation entry point that handles the ASP.NET Core platform and compare its output with the Webpack option. Done means the generated folder contains a runnable .NET Core project with C# files and `dotnet run` works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, typescript
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100