You might even be better off with a 'before:run'

because cypress-real-app seems to be seeding the database quite often

I don't think that works as expected for some reason: plugins/index.ts

ts
/**
 * @type {Cypress.PluginConfig}
 */
module.exports = (on: any, config: { env: { awsConfig: any } }) => {
  // AWS config
  config.env.awsConfig = awsconfig

  console.log('plugins') // this logs

  on('before:run', (details) => {
    setA('hello!') // This never seems to run
    console.log('hello')
  })

  return config
}

spec:

ts
import { getA } from '../../data/users'

describe('Login', () => {

  // Intercept all calls to Cognito, so we can stub the responses.
  // All OPTIONS (preflight) calls should be successful.
  beforeEach(() => {
    console.log(getA()) // logs null
    cy.visit('login')
  })

also console logging in the hook (like the docs do), never seems to show up, so I have a feeling it never actually runs

only

before:browser:launch

ever triggers

Oh, it needs the

experimentalInteractiveRunEvents

flag?

Probably, are you using the hooks in open mode?

theeeeere we go, yeah open mode is pretty much the go-to for when writing tests locally

doesn't seem to use ES modules though :/

some-module.ts

ts
const a = {
  foo: null,
}

export const setA = (val) => {
  a.foo = val
}

export const getA = () => a

plugin/index.ts

ts
import { setA } from '../some-module' 
module.exports = (on: any, config: { env: { awsConfig: any } }) => {
  on('before:run', (details) => {
    setA('hello!')
  })
}

test.spec.ts

ts
import { getA } from '../some-module'

describe('Login', () => {
  beforeEach(() => {
    console.log(getA()) // { foo: null } instead of { foo: 'hello!' }
  })
})

To run plugins, we use ts-node… which is as you can see transforming all modules into commonjs for compatibility…

Darn... I thought you said there was ES module support: https://discord.com/channels/755913899261296641/755913900024791046/869329195178811463

I did say that ts files are transformed

In theory you should have to worry about it

It’s only if you count on import.meta that you should face issues

My goal is really straightforward: I just want to seed data only once in a JS module, as it's dynamic (e.g. access tokens are generated based on the seed data)

In your plugins file you should use export default instead of module.export

ah good catch

no dice 😦

I wonder if the TS target messes it up

esnext

also doesn't work :/

Ok, I might be onto something

I only got it working in the plugin file, it seems spec files are not treated as modules :/

No they are not you are right

Unless… you use a preprocessor

Use TypeScript With Cypress | Better world by better software https://glebbahmutov.com/blog/use-typescript-with-cypress/

ok, let's give that a shot

no dice, just gets stuck here with no errors in the console

I'll just ditch it... Maybe at some point we get the option for full ES6 support. I think the demand for transpilation will fade as almost every browser supports ES modules