Remove exports field to fix eslint and build errors #393
+9
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix errors in nextcloud/server#34044
The eslint errors
import/no-unresolved
andnode/no-missing-import
are due to the lack of support for theexports
field, see import-js/eslint-plugin-import#1810 and mysticatea/eslint-plugin-node#255Switching from
to
fixes the eslint errors but results in new build errors coming from
babel-loader
This seems to be because
babel-loader
uses theexports
field exclusively when presentSo switching to the
dist
import in nextcloud/server#34044 and removing theexports
field in this package is needed to resolve the errors