You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are trying to bundle balena-sdk into an internal electron app we are writing. I'd expect Webpack and Babel to bundle these without any issues (like they do the rest of our dependency tree)
import{getSDK}from'balena-sdk'
Actual Behavior
The bundling fails when the balena-sdk and pinejs-client-corepackage.json files point to index.js, as the @balena/es-version module somehow gets in the way of webpack, which then tries to load the .d.ts, .map and .md files (even though they're ignored)
This can be worked around by providing aliases to the 2018 versions in the webpack config file:
Expected Behavior
We are trying to bundle
balena-sdk
into an internal electron app we are writing. I'd expect Webpack and Babel to bundle these without any issues (like they do the rest of our dependency tree)Actual Behavior
The bundling fails when the
balena-sdk
andpinejs-client-core
package.json
files point toindex.js
, as the@balena/es-version
module somehow gets in the way of webpack, which then tries to load the.d.ts
,.map
and.md
files (even though they're ignored)This can be worked around by providing aliases to the 2018 versions in the webpack config file:
Note that this also fails when trying to include the 2018 version of the
balena-sdk
, as then you hit issues downstream inpinejs-client-core
:Steps to Reproduce the Problem
Specifications
References
There's nothing special about our webpack file - this is just bundling the SDK into the Node.js side of electron:
Happy to test whatever required on my side
The text was updated successfully, but these errors were encountered: