You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@senssoft.apache.org by "Joshua Poore (JIRA)" <ji...@apache.org> on 2019/03/01 06:37:00 UTC
[jira] [Comment Edited] (SENSSOFT-340) UserALE.js fails to build on
Branch-336
[ https://issues.apache.org/jira/browse/SENSSOFT-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16781336#comment-16781336 ]
Joshua Poore edited comment on SENSSOFT-340 at 3/1/19 6:36 AM:
---------------------------------------------------------------
Have been unable to replicate this error:
Hypothesis 1: Uncaught breaking change in Gulp 4.0.0 migration.
Rebuilt from scratch with NPM 6.7.0 Node.js 11.1.0, Successfully
Hypotheses 2: Global Gulp/NPM settings cause different outcomes for different users
On my end, updated 'Engine' var in package.js for ~ NPM 6.7.0, ~ Node.js 11.1.0 (NPM, 6.5.0 should be comparable), rebuilt successfully.
Hypothesis 3: Global Rollup versions conflict with local userale.js packages, causing different outcomes for different users.
Updated Rollup from v 0.26 -> 1.3.2 (!!) and rollup-plugin-json. Breaking changes resolved in gulpfile. Tested script tag and plugins with new build. They function to expectation in chrome and firefox, consistent with SENSSOFT-192 branch.
Regression testing finds that Useralejs builds from SENSSOFT-192 through rollup with iife format are subtly different from those build in SENSSOFT-336, despite minimal syntax changes to this gulp/rollup task. Does not appear to be functionally different after unit and integration testing–seems to be inherent to modern version of rollup. Based on docs [1-2], userale.js rollup output is left as iify (optimized for script tags), other rollup outputs (ext) are left as esm modules.
was (Author: poorejc@me.com):
Have been unable to replicate this error:
Hypothesis 1: Uncaught breaking change in Gulp 4.0.0 migration.
Rebuilt from scratch with NPM 6.7.0 Node.js 11.1.0, Successfully
Hypotheses 2: Global Gulp/NPM settings cause different outcomes for different users
On my end, updated 'Engine' var in package.js for ~ 6.7.0, ~ Node.js 11.1.0 (NPM, 6.5.0 should be comparable), rebuilt successfully.
Hypothesis 3: Global Rollup versions conflict with local userale.js packages, causing different outcomes for different users.
Updated Rollup from v 0.26 -> 1.3.2 (!!) and rollup-plugin-json. Breaking changes resolved in gulpfile. Tested script tag and plugins with new build. They function to expectation in chrome and firefox, consistent with SENSSOFT-192 branch.
Regression testing finds that Useralejs builds from SENSSOFT-192 through rollup with iife format are subtly different from those build in SENSSOFT-336, despite minimal syntax changes to this gulp/rollup task. Does not appear to be functionally different after unit and integration testing–seems to be inherent to modern version of rollup. Based on docs [1-2], userale.js rollup output is left as iify (optimized for script tags), other rollup outputs (ext) are left as esm modules.
> UserALE.js fails to build on Branch-336
> ---------------------------------------
>
> Key: SENSSOFT-340
> URL: https://issues.apache.org/jira/browse/SENSSOFT-340
> Project: SensSoft
> Issue Type: Bug
> Components: UserALE.js
> Affects Versions: UserALE.js 2.0.0
> Environment: NPM v3.5.2 and v6.5.0, Node.js ??
> Reporter: Joshua Poore
> Assignee: Joshua Poore
> Priority: Critical
> Fix For: UserALE.js 2.0.0
>
>
> Following Gulp 4.0.0 update one user reports that userale.js will not build on SENSSOFT-336
> Ran on NPM v3.5.2 and v6.5.0
> Error at 'build-web-ext'
> Error Text: 'Error: Could not load null: path must be a string or Buffer'
> /npm-modules/rollup/dist. ...
> Rollup is clearly having trouble
> Not a common issue, very few tickets/stackexchange(s): [https://github.com/szwacz/electron-boilerplate/issues/102]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)