GraphQl工具LOADFILESSYNC适用于运行时，但在Nodejs中不适合开玩笑 - 为什么？

发布于 2025-01-29 06:19:07 字数 1232 浏览 3 评论 0原文

我正在努力设置Apollo GraphQl Server（基于Express），并使用本指南。这导致我使用loadFileSsync，path和提供的节点__ dirname。

我的Typedefs模块看起来像是这样的，

const path = require('path');
const { loadFilesSync } = require('@graphql-tools/load-files');
const { mergeTypeDefs } = require('@graphql-tools/merge');

const schemaDefsArray = loadFilesSync(
    path.join(__dirname, './types'),
    {
        recursive: true,
        extensions: ['graphql'],
    })

const typeDefs = mergeTypeDefs(schemaDefsArray);

module.exports = typeDefs;

我的设置是一个由docker容器构建的docker容器，该容器是从返回到Windows中的WSL文件系统的。 Apollo/Express Server和Jest测试均从该容器内部在节点上运行。

我的问题是，在常规运行时（基于Express的Apollo GraphQl Server），__ dirname是/srv/＆lt;项目名称根据预期解决模式。但是在测试运行期间（直接在节点上运行的玩笑）__ dirname是完全合格的\\ wsl $ \ ubuntu-20.04 \ home \ home \ home \＆gt; user name＆gt; \ projects＆gt; \ project ; \ src \ schema。 Apollo服务器加载，读取和解析架构罚款，而开玩笑测试试图通过同一模块加载相同文件的测试找不到目录。

为什么工作目录的解决方案有所不同，这对loadfiles函数意味着什么？我该如何解决？

原文

I am working on setting up an Apollo GraphQL Server (Express based) and use the pattern where .graphql files are loaded and merged as demonstrated in this guide. This leads me to use loadFilesSync, path and the Node provided __dirName.

My typedefs module looks like this

const path = require('path');
const { loadFilesSync } = require('@graphql-tools/load-files');
const { mergeTypeDefs } = require('@graphql-tools/merge');

const schemaDefsArray = loadFilesSync(
    path.join(__dirname, './types'),
    {
        recursive: true,
        extensions: ['graphql'],
    })

const typeDefs = mergeTypeDefs(schemaDefsArray);

module.exports = typeDefs;

My setup is a docker container built from a repo checked out to the WSL file system in Windows. Both the Apollo/Express server and Jest tests are run on Node from inside that container.

My problem is that during regular runtime (Express based Apollo GraphQL Server), __dirName is /srv/<project name>/src/schema and all .graphql-files are resolved for the schema as intended. But during test-runs (Jest running directly on Node) __dirName is a fully qualified \\wsl$\Ubuntu-20.04\home\<user name>\projects\<project name>\src\schema. The Apollo Server loads, reads, and resolves the schema fine while Jest tests attempting to load the same files through the same module cannot find the directory.

Why is the working directory resolved differently, what does it mean for the loadFiles function and how do I fix this?

分享到QQ

分享到微博