Skip to content
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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: resolve next-server from next app directory and not from plugin #2059

Merged
Merged
Show file tree
Hide file tree
Changes from 24 commits
Commits
Show all changes
34 commits
Select commit Hold shift + click to select a range
8d8d8ae
fix: resolve next-server from next app directory and not from plugin
pieh Apr 21, 2023
e7ae048
fix: update api handler
pieh Apr 21, 2023
15c1bdd
chore: export type from server module
pieh Apr 21, 2023
4b64c17
fix: server.spec.ts
pieh Apr 21, 2023
1933824
chore: move next server throwing to runtime
pieh Apr 21, 2023
e06157d
fix: restore trying to resolve from plugin and not appdir
pieh Apr 21, 2023
ffae6a2
fix: use relative import paths not absolute
pieh Apr 21, 2023
d50c047
fix: server.spec.ts (again)
pieh Apr 21, 2023
c5a4afd
fix: index.spec.ts
pieh Apr 21, 2023
48468bc
chore: diff cleanup
pieh Apr 21, 2023
33c28ae
fix: handle function config parsing as well
pieh Apr 25, 2023
be8bc6e
fix: adjust import
pieh Apr 25, 2023
caef767
fix: server.spec.ts (again vol 2)
pieh Apr 25, 2023
56aa4f7
test: add integration test
pieh Apr 26, 2023
1e48952
Merge remote-tracking branch 'origin/main' into fix/use-next-director…
pieh Apr 26, 2023
22e2fa2
test: log npm version
pieh Apr 26, 2023
6e229c9
test: install newer npm/node
pieh Apr 26, 2023
74ab70e
test: bump timeout for setup
pieh Apr 26, 2023
e4fadf4
test: ensure test page is ssr
pieh Apr 26, 2023
1774f47
refactor: get rid of unneded new helper
pieh Apr 26, 2023
bbff3a9
chore: cleanup some debugging logs
pieh Apr 27, 2023
ade1a2e
fix: add fallback in case findModuleBase will be false
pieh Apr 27, 2023
610d73f
refactor: use one-parameter object for makeHandler functions
pieh Apr 27, 2023
917d3ce
Merge remote-tracking branch 'origin/main' into fix/use-next-director…
pieh Apr 27, 2023
1b01485
Merge remote-tracking branch 'origin/main' into fix/use-next-director…
pieh Apr 28, 2023
04f3164
refactor: don't rely on MODULE_NOT_FOUND for lack of advanced API rou…
pieh Apr 28, 2023
92dcf3a
Update packages/runtime/src/templates/server.ts
pieh May 2, 2023
66a9670
fix: streamline no-shadow handling
pieh May 2, 2023
6e4d78a
Merge branch 'main' into fix/use-next-directory-when-resolving-server…
LekoArts May 3, 2023
8f71783
chore: automatic linting
LekoArts May 3, 2023
9efa6cb
chore: fix linting
LekoArts May 3, 2023
a92dbac
chore: post-commit linting :rolleyes:
LekoArts May 3, 2023
767dca9
Merge branch 'main' into fix/use-next-directory-when-resolving-server…
LekoArts May 3, 2023
40c6469
Merge branch 'main' into fix/use-next-directory-when-resolving-server…
LekoArts May 4, 2023
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
29 changes: 29 additions & 0 deletions .github/workflows/test-integration.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
name: Next Runtime Integration Tests
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not really integration test - it's really more e2e, but "e2e" is somewhat taken by tests we have copied from Next - so I went with integration for now, but maybe we just need to agree on how to refer to e2e tests that are not copied from next and I would love to adjust naming in this PR to reflect that

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it make sense to rename the Next tests 'upstream' tests?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I think it make sense, but at this point I'd rather ship those as-is and do renaming in separate standalone PR to not keep the fix hostage


on:
pull_request:
push:
branches: [main]

concurrency:
group: ${{ github.head_ref || github.run_id }}
cancel-in-progress: true

jobs:
build:
name: Integration tests
runs-on: ubuntu-latest

steps:
- uses: actions/checkout@v2
- name: Installing with LTS Node.js
uses: actions/setup-node@v2
with:
node-version: 18
check-latest: true
- name: Install netlify-cli and npm
run: npm install -g netlify-cli npm
- name: NPM Install
run: npm install
- name: Run integration tests
run: npm run test:integration