-
-
Notifications
You must be signed in to change notification settings - Fork 282
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
FormData import not working #1112
Conversation
This is blocking everything in the pipeline. For now, ill downgrade rollup to before 2.26 to see if that helps, and come back to this proper afterward |
0718da5
to
0b675b4
Compare
Still tackling this. Latest work includes:
using a test repo: src/index.ts import FormDataI from 'formdata-node'
const c = new FormDataI()
export { c } with a rollup config of : import resolve from '@rollup/plugin-node-resolve';
import commonjs from '@rollup/plugin-commonjs';
import json from '@rollup/plugin-json';
import nodePolyfills from 'rollup-plugin-node-polyfills';
import globals from 'rollup-plugin-node-globals';
import pkg from './package.json';
import ts from 'rollup-plugin-typescript2';
import typescript from 'typescript';
export default [
{
input: 'src/index.ts',
output: {
file: 'dist/out.js',
name: 'gitbeaker',
format: 'umd',
// exports: 'named',
},
plugins: [globals(), nodePolyfills(), json(), ts({ typescript, useTsconfigDeclarationDir: true }), resolve(), commonjs()],
},
]; Still trying to figure out how to fix this sigh |
Tracking error here |
Got everything to compile properly again! Just fixing up the unit tests now. |
Still running into an issue with the integration tests. Gonna go back to the drawing board and debug step by step |
Summary
The export of the FormData library seems to cause a problem when in combination of the latest rollup release.
I havent received any applicable feedback form-data/form-data/issues/470, form-data/form-data/issues/441
Possible solutions