My setup uses Nuxt 3 and all functionality up to no has worked great
When running yarn datocms migrations:run --destination=feature-branch --api-token=<TOKEN> I receive this error ‘Must use import to load ES Module’ (see terminal error in image below)
Having looked on the community threads there is a similar post but it was resolved over email in the end. Something obviously needs to change but having played with removing ‘type’: model from package.json and other quick fixes I’ve not found a solution.
Having looked on the community threads there is a similar post but it was resolved over email in the end. It would be great to get some help! Thanks in advance.
We shouldn’t be using require() in our migration scripts… can you please post 1707906087_createArticleModel.ts (or email us at support@datocms.com if you prefer) so we can see what it looks like? I wonder if maybe something in Nuxt (like a linter or bundler) is rewriting or rebundling our files…?
I believe this situation is caused by different code styles used in older vs newer JS: ES Modules · Nuxt Concepts so it might be kinda messy to disentangle, depending on how your codebase is set up.
If you don’t strictly need to have the migration files inside your main project repo (i.e., could it be a separate repo altogether, or a nested one inside a subfolder in your main one?), keeping those scripts separate from your main project might make them easier to maintain and run. They don’t really need to interact with your frontend anyway; they’re just standalone files that talk to our backend independently of whatever your frontend does.
import { Client } from '@datocms/cli/lib/cma-client-node';
export default async function(client: Client): Promise<void> {
// DatoCMS migration script
// For more examples, head to our Content Management API docs:
// https://www.datocms.com/docs/content-management-api
// Create an Article model:
// https://www.datocms.com/docs/content-management-api/resources/item-type/create
const articleModel = await client.itemTypes.create({
name: 'Article',
api_key: 'article',
});
// Create a Title field (required):
// https://www.datocms.com/docs/content-management-api/resources/field/create
const titleField = await client.fields.create(articleModel, {
label: 'Title',
api_key: 'title',
field_type: 'string',
validators: {
required: {},
},
});
// Create an Article record:
// https://www.datocms.com/docs/content-management-api/resources/item/create
const article = await client.items.create({
item_type: articleModel,
title: 'My first article!',
});
}
So that’s my biggest query really - there is no require() in this file. So I’m not sure if it is calling a function that includes require somewhere?
And to confirm this is the file created when following the docs command.
I haven’t linted or amended it in any way, so unsure why my repo would interfere. Appreciate the idea of storing these files in a different repo but we are looking to use Dato for multiple projects in the future so it would be really useful to properly get to the bottom of this or at least understand why the error is occurring. Thanks
Upon investigation, I think there might be a compatibility issue between our script and Nuxt’s tsconfig.json. I’ll report it to the devs for an investigation, but in the meantime, could you please try this workaround?
Make an empty file called empty.json (in your IDE, or just in the shell via touch empty.json)
Edit datocms.config.json and under migrations, add "tsconfig": "empty.json". The full config file should look something like this:
I attempted your empty.json trick but sadly still had the same error returned to me so looks like something else is causing the issue. Thanks again for the help!
Just wanted to check back in this issue. Did you ever try it without the "type": "module", line? We’re still trying to diagnose the root cause of this, but knowing your rationale for that would help.
We also released a new CLI version, v2.0.0 that makes it so that the migrations will use its own tsconfig (unless you override it). Hopefully that will help too, especially with type: module?
If you’re still having issues, could you please let us know?
)