Build broken - example component not rendering in Chrome, Firefox, IE11 neither on Windows 7, Windows 10 nor on Ubuntu 17.10.1 - only on Mac about stencil-component-starter HOT 24 CLOSED

I encounter the same problem on :

• stencil/core v0.9.1 and @stencil/core v0.9.7
• Node v10.2.1
• npm 5.6.0
• Mac 10.11.6
• Chrome 67, Firefox, Safari (didn't test on edge)

I'm not sure if it's normal but in www/build/mycomponent/mycomponent.core.js App.components is empty so defineComponent(cmpMeta, HostElementConstructor)is never called.

stencil-app-starteris not working either

EDIT For me, the problem was caused by my project being located under a test folder. The components was being ignored by the default excludeSrc configuration which compare [ '**/test/**', '**/*.spec.*' ] to absolute file path.

from stencil-component-starter.

Doesn't work on Ubuntu/Chrome either.

Chrome Screenshot

from stencil-component-starter.

Also fails using npm run dev on Chrome Version 65.0.3325.181 (Official Build) (64-Bit)/Ubuntu 17.10.1:

A bad HTTP response code (404) was received when fetching the script.
sw.js Failed to load resource: net::ERR_INVALID_RESPONSE

https://imgur.com/a/esg2g

from stencil-component-starter.

2nd try on Ubuntu 17.10.1

I tried going back to commit eb79892 which had Stencil core 0.7.6

Fresh install of the component starter, then npm run build --prod followed by npm run serve gives me

o70a0g6k.js:2 Uncaught (in promise) SyntaxError: Unexpected token export
    at Object.<anonymous> (workbox-core.dev.js:842)
    at Generator.next (<anonymous>)
    at step (workbox-core.dev.js:14)
    at workbox-core.dev.js:25
(anonymous) @ workbox-core.dev.js:842
step @ workbox-core.dev.js:14
(anonymous) @ workbox-core.dev.js:25

Node v8.11.1
npm 5.6.0

Chrome console error

from stencil-component-starter.

Will give it a third shot on Mac at home, in about 2 hours.

Update: It does work as expected on Mac OS High Sierra (latest version) using Firefox, Chrome, Safari and Opera (latest versions).

from stencil-component-starter.

Next attempt is gonna be Windows 10.

from stencil-component-starter.

@franktopel so so far, this is only breaking on Ubuntu right?

from stencil-component-starter.

Just making sure im following here. Same version of Node on every machine?

from stencil-component-starter.

Node v8.11.1 on all machines. Working only on Mac, but neither on Windows 7 nor on Ubuntu 17.10.1.

from stencil-component-starter.

Still updating Windows 10, might be only tomorrow when I can post whether it works on Windows 10.

from stencil-component-starter.

Just checked. Does not work on a freshly installed and updated Windows 10 system (latest Chromium).

from stencil-component-starter.

This is now the third Windows machine I'm testing this on, to no avail. 2x Windows 10, 1x Windows 7. I do have administrative rights on all machines.

I just counter-checked stencil-app-starter and that works with no problems on Windows 10.

from stencil-component-starter.

I have just tested on another Windows 10 machine using Node v6.14.1.

So I wasn't able to get it working on any Windows machine whatsoever.

This is a pity since I've been assigned the task to evaluate StencilJS for usage in a really large company for a migration project. Not the best start I'd say :(

Running npm run dev --es5 gives me

C:\iskv21c\webcomponents\stencil>npm run dev --es5

> [email protected] dev C:\iskv21c\webcomponents\stencil
> sd concurrent "stencil build --dev --watch" "stencil-dev-server"

[29:59.7]  @stencil/core v0.7.7 
[29:59.7]  build, mycomponent, dev mode, started ...
[29:59.9]  compile started ...
[30:13.3]  compile finished in 13.41 s

[ ERROR ]  typescript: C:/iskv21c/webcomponents/node_modules/@types/jasmine/index.d.ts, line: 14
           Duplicate identifier 'describe'.

     L15:   * A focused it

[ ERROR ]  typescript: C:/iskv21c/webcomponents/node_modules/@types/jasmine/index.d.ts, line: 15
           Duplicate identifier 'fdescribe'.

     L15:   * A focused it         
     L16:   * If suites or specs are focused, only those that are focused will be executed.

[ ERROR ]  typescript: C:/iskv21c/webcomponents/node_modules/@types/jasmine/index.d.ts, line: 16
           Duplicate identifier 'xdescribe'.

     L15:  * A focused it
     L16:  * If suites or specs are focused, only those that are focused will be executed.
     L17:  * @param expectation

[ ERROR ]  typescript: C:/iskv21c/webcomponents/node_modules/@types/jasmine/index.d.ts, line: 25
           Duplicate identifier 'it'.

     L25:   * Mark a spec as pending, expectation results will be ignored.
     L26:   * If you call the function pending anywhere in the spec body, no matter the expectations, the spec will be marked pending.

[ ERROR ]  typescript: C:/iskv21c/webcomponents/node_modules/@types/jasmine/index.d.ts, line: 34
           Duplicate identifier 'fit'.

     L33:  * Run some shared setup before each of the specs in the describe in which it is called.
     L34:  * @param action Function that contains the code to setup your specs.
     L35:  * @param timeout Custom timeout for an async beforeEach.

[ ERROR ]  typescript: C:/iskv21c/webcomponents/node_modules/@types/jasmine/index.d.ts, line: 35
           Duplicate identifier 'xit'.

     L34:  * @param action Function that contains the code to setup your specs.
     L35:  * @param timeout Custom timeout for an async beforeEach.

[ ERROR ]  typescript: C:/iskv21c/webcomponents/node_modules/@types/jasmine/index.d.ts, line: 50
           Duplicate identifier 'beforeEach'.

     L49:  * @param action Function that contains the code to setup your specs.
     L50:  * @param timeout Custom timeout for an async beforeAll.

[ ERROR ]  typescript: C:/iskv21c/webcomponents/node_modules/@types/jasmine/index.d.ts, line: 57
           Duplicate identifier 'afterEach'.

     L56:  * Note: Be careful, sharing the teardown from a afterAll makes it easy to accidentally leak state between your specs so that they erroneou
sly pass or fail.
     L57:  * @param action Function that contains the code to teardown your specs.
     L58:  * @param timeout Custom timeout for an async afterAll

[ ERROR ]  typescript: C:/iskv21c/webcomponents/node_modules/@types/jasmine/index.d.ts, line: 65
           Duplicate identifier 'beforeAll'.

     L64:   * @param spy
     L66:  declare function expect(spy: Function): jasmine.Matchers<any>;

[ ERROR ]  typescript: C:/iskv21c/webcomponents/node_modules/@types/jasmine/index.d.ts, line: 73
           Duplicate identifier 'afterAll'.

     L72:  declare function expect<T>(actual: ArrayLike<T>): jasmine.ArrayLikeMatchers<T>;

[ ERROR ]  typescript: C:/iskv21c/webcomponents/node_modules/@types/jasmine/index.d.ts, line: 79
           Cannot redeclare block-scoped variable 'expect'.

     L78:  declare function expect<T>(actual: T): jasmine.Matchers<T>;

[ ERROR ]  typescript: C:/iskv21c/webcomponents/node_modules/@types/jasmine/index.d.ts, line: 134
           Duplicate identifier 'clock'.

    L134:      function createSpyObj(baseName: string, methodNames: any[] | {[methodName: string]: any}): any;
    L135:      function createSpyObj<T>(baseName: string, methodNames: any[] | {[methodName: string]: any}): SpyObj<T>;

[30:13.3]  build failed, watching for changes... in 13.65 s

from stencil-component-starter.

Hey @franktopel , sorry about the issues you're running into, this is on me. From the errors your getting, it looks like your running an old version of Stencil. That would not surprise me as I currently have this starter set to an old version of Stencil. I am going to update this starter, double check it works locally on my machine and then I will ping you here so you can give it a go. Also, if you would like, you can join the Stencil slack https://stencil-worldwide.herokuapp.com/. I try to be available on there at all times (my username is Justin Willis). Thanks for trying out Stencil!

from stencil-component-starter.

@franktopel Alright, ive updated the starter locally and everything seems to be working on my Windows 10 machine. Going to do a few more tests and then ill push the updates.

from stencil-component-starter.

Testing of both a prod build and dev build went well. I just updated this starter to the latest and also updated the config some. Let me know if everything is working for you (:

from stencil-component-starter.

Thanks alot for your quick reaction. On 4 different windows machines I was getting 4 different behaviours - are you sure this can be fixed by updating some version? As the company I'm evaluating Stencil for comes from the Java/Swing world they are deeply rooted in Windows, and they are looking for a technology that will work for the next 15+ years. Noone will even consider changing the OS here. I will try at work tomorrow and report how it goes.

from stencil-component-starter.

I just tested on Windows 7 Professional 64 bit, latest Chrome, and IE11. It fails.

from stencil-component-starter.

Re-tested on Ubuntu 17.10.1 / latest Chrome using npm run dev --es5. # It fails.

from stencil-component-starter.

It also fails using npm run build && npm run serve (Ubuntu 17.10.1/ latest Chrome). The element is never registered.

Node / npm version:

from stencil-component-starter.

@franktopel So one of our goals with Stencil is to make sure that 1. it always works everywhere and 2. we always keep breaking changes to a minimal. There were some build issues with older versions, but they had been fixed in the latest version, which is why I updated it. Debugging more today

from stencil-component-starter.

After we got it to work on a Macbook running Windows 10 in Bootcamp during a teamviewer session (which at first did not work but suddenly did, and neither me nor @jgw96 had any explanation for the weird behaviour) , I tried on two different machines since then, one running Windows 8.1, the other running Windows 10. Both received fresh installs of Nodejs 8.11.1, on both machines it failed silently, meaning the build works, but the component never registers, rendering the page blank with no console errors whatsoever. This is true for both npm run dev and npm run dev --es5. I have checked in Chrome, IE11 and Opera.

from stencil-component-starter.

Hello, i unfortunately notice same issue on mac with following setup :

• Node v9.2.0
• npm 5.5.1
• stencil 0.7.22 or 0.7.27

let me know if i can help

from stencil-component-starter.

I just tested this using the latest version of this starter on Mac, Linux, and Windows using both the stable and LTS versions of node. It worked in all cases, so I am going to close this.

from stencil-component-starter.