Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

pavelsavara
Copy link
Member

@pavelsavara pavelsavara commented Mar 14, 2023

Split off from #83364
Contributes to #72990
Contributes to #85045

  • drop dotnet.es6.post.js
  • simplify dotnet.es6.lib.js and dotnet.es6.extpost.js and dotnet.es6.pre.js
  • create types-api.ts by moving types from other files
  • drop export_linker() from startup
  • drop IMPORTS object
  • drop isGlobal flag (CJS cleanup)
  • reorganized init_polyfills_async and init_replacements
  • refactored unifyModuleConfig from dotnet.es6.pre.js to run-outer.ts
  • removed INTERNAL from top most export

@pavelsavara pavelsavara added this to the 8.0.0 milestone Mar 14, 2023
@pavelsavara pavelsavara requested a review from maraf March 14, 2023 18:55
@pavelsavara pavelsavara self-assigned this Mar 14, 2023
@ghost
Copy link

ghost commented Mar 14, 2023

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

Split off from #83364

  • drop dotnet.es6.post.js and dotnet.es6.pre.js
  • simplify dotnet.es6.lib.js and dotnet.es6.extpost.js
  • create types-api.ts by moving types from other files
  • drop export_linker() from startup
  • drop IMPORTS object
  • drop isGlobal flag (CJS cleanup)
  • reorganized init_polyfills_async and init_replacements
  • moved createDotnetRuntime from dotnet.es6.pre.js to run-outer.ts
  • removed INTERNAL from top most export
Author: pavelsavara
Assignees: pavelsavara
Labels:

arch-wasm, area-System.Runtime.InteropServices.JavaScript

Milestone: 8.0.0

@pavelsavara
Copy link
Member Author

/azp run runtime-wasm

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@pavelsavara
Copy link
Member Author

@radical I would appreciate your help with Wasm.Build.Tests on this branch. There are CI failures, but locally it works for me.

@pavelsavara
Copy link
Member Author

/azp run runtime-wasm

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@pavelsavara
Copy link
Member Author

/azp run runtime-wasm

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@pavelsavara pavelsavara force-pushed the browser_modules_prep1 branch from 964b98f to 54e9f48 Compare April 26, 2023 12:42
@pavelsavara pavelsavara force-pushed the browser_modules_prep1 branch from 54e9f48 to 55edc8b Compare April 26, 2023 15:32
@pavelsavara pavelsavara marked this pull request as ready for review April 27, 2023 12:18
@pavelsavara
Copy link
Member Author

/azp run runtime-wasm

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@pavelsavara
Copy link
Member Author

All the CI failures are unrelated.

Copy link
Member

@maraf maraf left a comment

Choose a reason for hiding this comment

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

It looks great! I have just some minor questions

- renamed imports.ts to globals.ts
- formatted jiterp code
@pavelsavara
Copy link
Member Author

/azp run runtime-wasm

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Member

@maraf maraf left a comment

Choose a reason for hiding this comment

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

Looks good to me 👍

@pavelsavara pavelsavara merged commit e6924ee into dotnet:main Apr 28, 2023
@ghost ghost locked as resolved and limited conversation to collaborators May 28, 2023
@pavelsavara pavelsavara deleted the browser_modules_prep1 branch September 2, 2024 15:30
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants