Export Feature does not work!

[parkychow]

I export the source code of "https://stackblitz.com/angular/ggqreenqvae?file=app%2Ftable-selection-example.ts"

When I run "ng server", it has error... it seems using webpack is very trouble while default Angular CLI is working properly.

RROR in Error: Tried to find bootstrap code, but could not. Specify either statically analyzable bootstrap code or pass in an entryModule to
the plugins options.
at Object.resolveEntryModuleFromMain (C:\code\TablewithSelection\node_modules@ngtools\webpack\src\entry_resolver.js:131:11)
at Promise.resolve.then.then (C:\code\TablewithSelection\node_modules@ngtools\webpack\src\angular_compiler_plugin.js:240:54)
at
at process._tickCallback (internal/process/next_tick.js:188:7)

[flyer1]

I was getting errors b/c inside the src folder was another src folder. The latter had my app folder in there plus some others. I moved all that was in the latter to the former (ie: combined the 2 src folders into 1) and this resolved the issue.

[intergalactickraigor]

Stackblitz still exports nested src folders.

Is this issue going to be resolved? I am seeing this problem too. And it is also causing problems with Angular's examples as seen in Angular's repository.

#angular/angular#23962

[intergalactickraigor]

nested src folders on Angular projects. It will not work unless you rearrange the files before running commands.

[ChenReuven]

@intergalactickraigor Thanks it working :)

[intergalactickraigor]

I submitted a pull request to attempt to resolve this to the stackblitz/angular-cli repository: stackblitz/angular-cli-template#7
however, I just noticed that the default angular application is now using angular 6, so I am not sure if this repository is still the source of truth for the starters.

Regardless, the issue is that blitz_export.json needs to not output to "src", as this folder is generated with a package.json and everything. It should export to "/" .

[methodbox]

EDIT: While the below works just fine and gives you a nice clean project, you can also just follow this guide:

https://angular.io/start/deployment - which requires just creating a new app with ng-cli (just use ng new my-app) and replacing the output app's src folder with the one you downloaded from StackBlitz.
However, this still won't work until you do the edit to polyfills.ts as mentioned below because core-js node module's path has changed slightly.

Hope that helps.

I had this same issue. I wanted to use the latest Angular 8 as well. Here's my solution.

Export the project normally by just downloading and extracting the zip. Replace dependencies and devDependencies by making note of all the deps and installing them individually (commands below).

This will install them @ latest versions.

npm install --save rxjs tslib core-js zone.js jasmine-core @angular/core @angular/forms @angular/common @angular/router jasmine-marbles @angular/compiler web-animations-js @angular/animations @angular/platform-browser angular-in-memory-web-api @angular/platform-browser-dynamic

npm install --save-dev @angular-devkit/build-angular @angular/cli @angular/compiler-cli @angular/language-service @types/jasmine @types/jasminewd2 @types/node codelyzer jasmine-core jasmine-spec-reporter karma karma-chrome-launcher karma-coverage-istanbul-reporter karma-jasmine karma-jasmine-html-reporter protractor ts-node tslint typescript

Modify the angular.json file to reference the tsconfig.app.json in the correct location. Edit the tsconfig value under the architect block.

...
"architect": {
        "build": {
          "builder": "@angular-devkit/build-angular:browser",
          "options": {
            "outputPath": "dist",
            "index": "src/index.html",
            "main": "src/main.ts",
            "polyfills": "src/polyfills.ts",
            "tsConfig": "src/tsconfig.app.json",
            ...

Edit the src/polyfills.ts file to reference the latest core-js module.

import 'core-js/es/reflect';
//import 'core-js/es7/reflect';

Then you can serve the app with npm start and it will run on localhost:4200 - I'm putting this here because there's no output indicating where the hell it's running ;).

Hope that helps.

[kc0tlh]

This should be resolved in our new VS Code editor. More information in Github issue #9